From 401cb123c02afd240f55f8dfa6d467e8c4ab4985 Mon Sep 17 00:00:00 2001 From: qianmigntian Date: Wed, 19 Feb 2020 15:50:43 +0800 Subject: [PATCH 1/2] Translated by qianmingtian --- .../20200217 How to install Vim plugins.md | 177 ------------------ .../20200217 How to install Vim plugins.md | 167 +++++++++++++++++ 2 files changed, 167 insertions(+), 177 deletions(-) delete mode 100644 sources/tech/20200217 How to install Vim plugins.md create mode 100644 translated/tech/20200217 How to install Vim plugins.md diff --git a/sources/tech/20200217 How to install Vim plugins.md b/sources/tech/20200217 How to install Vim plugins.md deleted file mode 100644 index 3b9f77a8c3..0000000000 --- a/sources/tech/20200217 How to install Vim plugins.md +++ /dev/null @@ -1,177 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (qianmingtian) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (How to install Vim plugins) -[#]: via: (https://opensource.com/article/20/2/how-install-vim-plugins) -[#]: author: (Seth Kenlon https://opensource.com/users/seth) - -How to install Vim plugins -====== -Whether you install them manually or with a package manager, plugins can -help you create the perfect Vim for your workflow. -![Team checklist and to dos][1] - -While [Vim][2] is fast and efficient, by default, it is but a mere text editor. At least, that's what it would be without plugins, which build upon Vim and add extra features to make it so much more than just a window for typing text. With the right mix of plugins, you can take control of your life and forge your own unique Vim experience. You can [customize your theme][3], and you can add syntax highlighting, code linting, version trackers, and much much more. - -### How to install Vim plugins - -Vim is extensible through plugins, but for a long time, there was no official method for installing them. As of the Vim 8.x series, however, there's a structure around how plugins are intended to be installed and loaded. You may encounter old instructions online or in project README files, but as long as you're running Vim 8 or greater, you should install according to Vim's [official plugin install method][4] or with a Vim package manager. You can use a package manager regardless of what version you run (including releases older than 8.x), which makes the install process easier than maintaining updates yourself. - -Both the manual and automated methods are worth knowing, so keep reading to learn about both. - -### Install plugins manually (Vim 8 and above) - -A Vim package is a directory containing one or more plugins. By default, your Vim settings are contained in **~/.vim**, so that's where Vim looks for plugins when you launch it. (The examples below use the generic name **vendor** to indicate that the plugins are obtained from an entity that is not you.) - -When you start Vim, it first processes your **.vimrc** file, and then it scans all directories in **~/.vim** for plugins contained in **pack/*/start**. - -By default, your **~/.vim** directory (if you even have one) has no such file structure, so set that up with: - - -``` -`$ mkdir -p ~/.vim/pack/vendor/start` -``` - -Now you can place Vim plugins in **~/.vim/pack/vendor/start**, and they'll automatically load when you launch Vim. - -For example, try installing [NERDTree][5], a text-based file manager for Vim. First, use Git to clone a snapshot of the NERDTree repository: - - -``` -$ git clone --depth 1 \ -  \ -  ~/.vim/pack/vendor/start/nerdtree -``` - -Launch Vim or gvim, and type this command: - - -``` -`:NERDTree` -``` - -A file tree will open along the left side of your Vim window. - -![NERDTree plugin][6] - -If you don't want a plugin to load automatically every time you launch Vim, you can create an **opt** directory within your **~/.vim/pack/vendor** directory: - - -``` -`$ mkdir ~/.vim/pack/vendor/opt` -``` - -Any plugins installed into **opt** are available to Vim but not loaded into memory until you add them to a session with the **packadd** command, e.g., for an imaginary plugin called foo: - - -``` -`:packadd foo` -``` - -Officially, Vim recommends that each plugin project gets its own directory within **~/.vim/pack**. For example, if you were to install the NERDTree plugin and the imaginary foo plugin, you would create this structure: - - -``` -$ mkdir -p ~/.vim/pack/NERDTree/start/ -$ git clone --depth 1 \ -  \ -  ~/.vim/pack/NERDTree/start/NERDTree -$ mkdir -p ~/.vim/pack/foo/start/ -$ git clone --depth 1 \ -  \ -  ~/.vim/pack/foo/start/foo -``` - -Whether that's convenient is up to you. - -### Using a Vim package manager (any Vim version) - -Since Vim series 8, package managers have become less useful, but some users still prefer them because of their ability to auto-update several plugins. There are several package managers to choose from, and they're each different, but [vim-plug][7] has some great features and the best documentation of them all, which makes it easy to start with and to explore in depth later. - -#### Installing plugins with vim-plug - -Install vim-plug so that it auto-loads at launch with: - - -``` -$ curl -fLo ~/.vim/autoload/plug.vim --create-dirs \ -  -``` - -Create a **~/.vimrc** file (if you don't have one already), and enter this text: - - -``` -call plug#begin() -Plug 'preservim/NERDTree' -call plug#end() -``` - -Each time you want to install a plugin, you must enter the name and location of the plugin between the **plug#begin()** and **plug#end** lines. (The NERDTree file manager is used above as an example.) If the plugin you want isn't hosted on GitHub, then you can provide the full URL instead of just the GitHub username and project ID. You can even "install" local plugins outside of your **~/.vim** directory. - -Finally, start Vim and prompt vim-plug to install the plugins listed in **~/.vimrc**: - - -``` -`:PlugInstall` -``` - -Wait for the plugins to be downloaded. - -#### Update plugins with vim-plug - -Editing **~/.vimrc** and issuing a command to do the installation probably doesn't seem like much of a savings over the manual install process, but the real benefit to vim-plug is in updates. To update all installed plugins, issue this Vim command: - - -``` -`:PlugUpdate` -``` - -If you don't want to update all plugins, you can update any subset by adding the plugin's name: - - -``` -`:PlugUpdate NERDTree` -``` - -#### Restore plugins - -Another vim-plug benefit is its export and recovery function. As any Vim user knows, the way Vim works is often unique to each user—in part because of plugins. Once you get the right blend of plugins installed and configured, the last thing you want is to lose track of them. - -Vim-plug has this command to generate a script for restoring all current plugins: - - -``` -`:PlugSnapshot ~/vim-plug.list` -``` - -There are many other functions for vim-plug, so refer to its [project page][7] for the full documentation. - -### Create the perfect Vim - -When you spend all day in a program, you want every little detail to serve you the best it possibly can. Get to know Vim and its many plugins until you build the perfect application for what you do. - -Got a favorite Vim plugin? Tell us all about it in the comments! - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/20/2/how-install-vim-plugins - -作者：[Seth Kenlon][a] -选题：[lujun9972][b] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/seth -[b]: https://github.com/lujun9972 -[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/todo_checklist_team_metrics_report.png?itok=oB5uQbzf (Team checklist and to dos) -[2]: https://www.vim.org/ -[3]: https://opensource.com/article/19/12/colors-themes-vim -[4]: https://github.com/vim/vim/blob/03c3bd9fd094c1aede2e8fe3ad8fd25b9f033053/runtime/doc/repeat.txt#L515 -[5]: https://github.com/preservim/nerdtree -[6]: https://opensource.com/sites/default/files/uploads/vim-nerdtree.jpg (NERDTree plugin) -[7]: https://github.com/junegunn/vim-plug diff --git a/translated/tech/20200217 How to install Vim plugins.md b/translated/tech/20200217 How to install Vim plugins.md new file mode 100644 index 0000000000..88b5779b0f --- /dev/null +++ b/translated/tech/20200217 How to install Vim plugins.md @@ -0,0 +1,167 @@ +[#]: collector: (lujun9972) +[#]: translator: (qianmingtian) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (How to install Vim plugins) +[#]: via: (https://opensource.com/article/20/2/how-install-vim-plugins) +[#]: author: (Seth Kenlon https://opensource.com/users/seth) + +如何安装 Vim 插件 +====== + +无论你是手动安装还是通过包管理器安装，插件都可以帮你为你的工作流中打造一个完美的 Vim 。 +![Team checklist and to dos][1] + +虽然 [Vim][2] 是快速且高效的，但在默认情况下，它仅仅只是一个文本编辑器。至少，这就是没有插件的情况 Vim 应当具备的样子，插件构建在 Vim 之上，并添加额外的功能，使 Vim 不仅仅是一个输入文本的窗口。有了合适的插件组合，你可以控制你的生活，形成你自己独特的 Vim 体验。你可以[自定义你的主题][3]，你可以添加语法高亮，代码 linting ，版本跟踪器等等。 + +### 怎么安装 Vim 插件 + +Vim 可以通过插件进行扩展，但很长一段时间以来，并没有官方的安装方式去安装这些插件。从 Vim 8 开始，有一个关于插件如何安装和加载的结构。你可能会在网上或项目自述文件中遇到旧的说明，但只要你运行 Vim 8 或更高版本，你应该根据 Vim 的[官方插件安装方法][4]安装或使用 Vim 包管理器。您可以使用包管理器，无论你运行的是什么版本(包括比 8.x 更老的版本)，这使得安装过程比您自己维护更新更容易。 + +手动和自动安装方法都值得了解，所以请继续阅读以了解这两种方法。 + +### 手动安装插件（ Vim 8 及以上版本） + +Vim 包是一个包含一个或多个插件的目录。默认情况下，你的 Vim 设置包含在 **~/vim** 中，这是 vim 在启动时寻找插件的地方。(下面的示例使用了通用名称 **vendor** 来表示插件是从一个不是你的实体获得的。) + +当你启动 Vim 时，它首先处理你的 **.vimrc**文件，然后扫描 **~/.vim** 中的所有目录查找包含在 **pack/*/start** 中的插件。 + +默认情况下，你的 **~/.vim** 目录(如果你有一个)没有这样的文件结构，所以设置为: + +``` +`$ mkdir -p ~/.vim/pack/vendor/start` +``` + +现在，你可以将 Vim 插件放在 **~/.vim/pack/vendor/start** 中，它们会在你启动 Vim 时自动加载。 + +例如，尝试安装一下 [NERDTree][5] ，一个基于文本的 Vim 文件管理器。首先，使用 Git 克隆 NERDTree 存储库的快照: + + +``` +$ git clone --depth 1 \ +  \ +  ~/.vim/pack/vendor/start/nerdtree +``` + +启动 Vim 或者 gvim ,然后键入如下命令： + + +``` +`:NERDTree` +``` + +Vim 窗口左侧将打开一个文件树。 + +![NERDTree plugin][6] + +如果你不想每次启动 Vim 时自动加载插件，你可以在 **~/.vim/pack/vendor** 中创建 **opt** 文件夹： + +``` +`$ mkdir ~/.vim/pack/vendor/opt` +``` + +任何安装到 **opt** 的插件都可被 Vim 使用，但是只有当你使用 **packadd** 命令将它们添加到一个会话中时，它们才会被加载到内存中。例如，一个虚构的叫 foo 的插件： + +``` +`:packadd foo` +``` + +Vim 官方建议每个插件项目在 **~/.Vim /pack** 中有自己的目录。例如，如果你要安装 NERDTree 插件和假想的 foo 插件，你需要创建这样的目录结构: + +``` +$ mkdir -p ~/.vim/pack/NERDTree/start/ +$ git clone --depth 1 \ +  \ +  ~/.vim/pack/NERDTree/start/NERDTree +$ mkdir -p ~/.vim/pack/foo/start/ +$ git clone --depth 1 \ +  \ +  ~/.vim/pack/foo/start/foo +``` + +这样做是否方便取决于你。 + +### 使用 Vim 包管理器（任何 Vim 版本） + +自从 Vim 8 以后，包管理器变得不那么有用了，但是一些用户仍然喜欢它们，因为它们能够自动更新一些插件。有几个包管理器可供选择，并且它们各不相同，但是 [vim-plug][7] 有一些很棒的特性和最好的文档，这使我们很容易开始并在以后深入研究。 + +#### 使用 vim-plug 安装插件 + +安装 vim-plug ，以便它在启动时自动加载： + +``` +$ curl -fLo ~/.vim/autoload/plug.vim --create-dirs \ +  +``` + +创建一个 **~/.vimrc** 文件（如果你还没有文件），然后输入以下文本： + +``` +call plug#begin() +Plug 'preservim/NERDTree' +call plug#end() +``` + +每次要安装插件时，都必须在 **plug＃begin()** 和 **plug＃end()** 之间输入插件的名称和位置（上面以 NERDTree 文件管理器为例。）。如果你所需的插件未托管在 GitHub 上，你可以提供完整的URL，而不仅仅是 GitHub 用户名和项目 ID 。你甚至可以在 **~/.vim** 目录之外“安装”本地插件。 + +最后，启动 Vim 并提示 vim-plug 安装 **~/.vimrc** 中列出的插件： + +``` +`:PlugInstall` +``` + +等待插件下载。 + +#### 通过 vim-plug 更新插件 + +与手动安装过程相比，编辑 **~/.vimrc** 并使用命令来进行安装可能看起来并没有多省事，但是 vim-plug 的真正优势在更新。更新所有安装的插件，使用这个 Vim 命令: + +``` +`:PlugUpdate` +``` + +如果你不想更新所有的插件，你可以通过添加插件的名字来更新任何插件: + +``` +`:PlugUpdate NERDTree` +``` + +#### 恢复插件 + +vim-plug 的另一个优点是它的导出和恢复功能。 Vim 用户都知道，正是插件的缘故，通常每个用户使用 Vim 的工作方式都是独一无二的。一旦你安装和配置了正确的插件组合，你最不想要的就是再也找不到它们。 + +Vim-plug 有这个命令来生成一个脚本来恢复所有当前的插件: + +``` +`:PlugSnapshot ~/vim-plug.list` +``` +vim-plug 还有许多其他的功能，所以请参考它的[项目页面][7]以获得完整的文档。 + +### 打造一个完美的 Vim + +当你整天都在做一个项目时，你希望每一个小细节都能为你提供最好的服务。了解 Vim 和它的许多插件，直到你为你所做的事情构建出一个完美的应用程序。 + +有喜欢的 Vim 插件吗？请在评论中告诉我们吧! + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/20/2/how-install-vim-plugins + +作者：[Seth Kenlon][a] +选题：[lujun9972][b] +译者：[qianmingtian][c] +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/seth +[b]: https://github.com/lujun9972 +[c]: https://github.com/qianmingtian +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/todo_checklist_team_metrics_report.png?itok=oB5uQbzf (Team checklist and to dos) +[2]: https://www.vim.org/ +[3]: https://opensource.com/article/19/12/colors-themes-vim +[4]: https://github.com/vim/vim/blob/03c3bd9fd094c1aede2e8fe3ad8fd25b9f033053/runtime/doc/repeat.txt#L515 +[5]: https://github.com/preservim/nerdtree +[6]: https://opensource.com/sites/default/files/uploads/vim-nerdtree.jpg (NERDTree plugin) +[7]: https://github.com/junegunn/vim-plug From 7d2a980c2839832687ef3d2670bd3e4e99c913b9 Mon Sep 17 00:00:00 2001 From: qianmigntian Date: Wed, 19 Feb 2020 15:58:43 +0800 Subject: [PATCH 2/2] Translated by qianmigntian and fix some error --- translated/tech/20200217 How to install Vim plugins.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/translated/tech/20200217 How to install Vim plugins.md b/translated/tech/20200217 How to install Vim plugins.md index 88b5779b0f..b21da86139 100644 --- a/translated/tech/20200217 How to install Vim plugins.md +++ b/translated/tech/20200217 How to install Vim plugins.md @@ -23,7 +23,7 @@ Vim 可以通过插件进行扩展，但很长一段时间以来，并没有官 ### 手动安装插件（ Vim 8 及以上版本） -Vim 包是一个包含一个或多个插件的目录。默认情况下，你的 Vim 设置包含在 **~/vim** 中，这是 vim 在启动时寻找插件的地方。(下面的示例使用了通用名称 **vendor** 来表示插件是从一个不是你的实体获得的。) +Vim 包是一个包含一个或多个插件的目录。默认情况下，你的 Vim 设置包含在 **~/.vim** 中，这是 vim 在启动时寻找插件的地方。(下面的示例使用了通用名称 **vendor** 来表示插件是从一个不是你的实体获得的。) 当你启动 Vim 时，它首先处理你的 **.vimrc**文件，然后扫描 **~/.vim** 中的所有目录查找包含在 **pack/*/start** 中的插件。 @@ -103,7 +103,7 @@ Plug 'preservim/NERDTree' call plug#end() ``` -每次要安装插件时，都必须在 **plug＃begin()** 和 **plug＃end()** 之间输入插件的名称和位置（上面以 NERDTree 文件管理器为例。）。如果你所需的插件未托管在 GitHub 上，你可以提供完整的URL，而不仅仅是 GitHub 用户名和项目 ID 。你甚至可以在 **~/.vim** 目录之外“安装”本地插件。 +每次要安装插件时，都必须在 **plug＃begin()** 和 **plug＃end()** 之间输入插件的名称和位置（上面以 NERDTree 文件管理器为例。）。如果你所需的插件未托管在 GitHub 上，你可以提供完整的 URL ，而不仅仅是 GitHub 用户名和项目 ID 。你甚至可以在 **~/.vim** 目录之外“安装”本地插件。 最后，启动 Vim 并提示 vim-plug 安装 **~/.vimrc** 中列出的插件：