blocks|key|95605|text|安装vim并将所有插件克隆到/etc/vim/plugin|type|blockquote|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|95606|这是行不通的，即使是在一台物理机器上。|unstyled|95607|Vim的运行时文件是以一种在所有级别上都是一致的特定方式排列的，因此将您的文件随机放置在任意位置不会对您有任何好处，因为没有任何东西会达到预期的位置。|95608|在这个特定的例子中，plugin/sonokai/autoload/airline/themes/sonokai.vim是一个自动加载的脚本，但是，因为你天真地把它放在plugin/下，所以它是作为一个全局插件提供的，这只会带来麻烦。|95609|Vim允许您为组织目的在plugin/下创建目录层次结构，但这些子目录仅用于全局插件。文件类型插件、语法脚本、缩进脚本、自动加载脚本等与此无关，因此必须将它们移到适当的目录下：ftplugin/、syntax/等。|95610|这种机制导致了这样一种情况，对于给定的第三方插件foo，您会得到分散在以下地方的文件：|95611|plugin/foo/foo.vim
syntax/foo/foo.vim
+++++++bar/bar.vim
indent/foo/foo.vim
+++++++bar/bar.vim
etc.|code-block|syntax|javascript|95612|它在技术上是可行的，如果你没有太多的插件，它甚至可能是可用的，但它本质上是混乱的。|95613|现在，处理插件的首选方法是通过新的:help+package特性。在不过分破坏文档的情况下，Vim的运行时中有一个名为pack的新目录，您可以在该目录下放置整个第三方插件，每个插件都位于自己的目录中，这基本上就是您在plugin/中尝试和失败的地方。因此，与上面的布局不同，您应该有：|95614|"+one+directory+for+plugin+`foo`
pack/<whatever>/start/foo/plugin/foo.vim
++++++++++++++++++++++++++indent/foo.vim
++++++++++++++++++++++++++syntax/foo.vim
"+and+one+directory+for+plugin+`bar`
pack/<whatever>/start/bar/indent/bar.vim
++++++++++++++++++++++++++syntax/bar.vim|95615|在正常用户的正常设置中，应该在pack目录下创建该目录。在这种特殊情况下，正确的位置几乎肯定是$VIM/vimfiles/。$VIM的确切值取决于许多事情，因此您必须询问Vim它在哪里：|95616|:echo+$VIM|95617|并相应地调整安装脚本。|95618|不过，我不确定集装箱化Vim的好处。|95619|entityMap^0|E|F|0|0|0|A|1E|2C|7|0|C|7|2G|9|2Q|7|0|O|3|0|0|0|H|D|1N|4|30|7|0|0|F|4|1B|E|1Q|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1E|8|@]|D|@]|E|$]]|$1|I|3|J|5|H|7|1F|8|@]|D|@]|E|$]]|$1|K|3|L|5|H|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|O|3|P|5|H|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1V|8|@]|D|@]|E|$T|U]]|$1|V|3|W|5|H|7|1W|8|@]|D|@]|E|$]]|$1|X|3|Y|5|H|7|1X|8|@$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]|$9|22|A|23|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|S|7|24|8|@]|D|@]|E|$T|U]]|$1|11|3|12|5|H|7|25|8|@$9|26|A|27|B|C]|$9|28|A|29|B|C]|$9|2A|A|2B|B|C]]|D|@]|E|$]]|$1|13|3|14|5|S|7|2C|8|@]|D|@]|E|$T|U]]|$1|15|3|16|5|H|7|2D|8|@]|D|@]|E|$]]|$1|17|3|18|5|H|7|2E|8|@]|D|@]|E|$]]|$1|19|3|-4|5|H|7|2F|8|@]|D|@]|E|$]]]|1A|$]]

<blockquote>
install vim and clone all the plugins to <code>/etc/vim/plugin</code>
</blockquote>
This wouldn't work, even on a physical machine.
Vim's runtime files are laid out in a specific way that is expected to be consistent at all levels so putting your files in random arbitrary locations won't do you any good because nothing will be where it is expected to be.
In this specific case, <code>plugin/sonokai/autoload/airline/themes/sonokai.vim</code> is an autoloaded script but, because you naïvely put it under <code>plugin/</code>, it is sourced as a global plugin, which can only create trouble.
Vim allows you to create directory hierarchies under <code>plugin/</code> for organisational purpose but those subdirectories are for global plugins only. Filetype plugins, syntax scripts, indent scripts, autoloaded scripts, etc. have nothing to do there so they must be moved under the appropriate directory: <code>ftplugin/</code>, <code>syntax/</code>, etc.
That mechanism leads to a situation where, for a given third-party plugin <code>foo</code> you would get files scattered around:
<pre><code>plugin/foo/foo.vim
syntax/foo/foo.vim
 bar/bar.vim
indent/foo/foo.vim
 bar/bar.vim
etc.
</code></pre>
It works, technically, and it might even be usable if you don't have too many plugins, but it is inherently messy.
Nowadays, the preferred way to handle plugins is via the newish <code>:help package</code> feature. Without spoiling the doc too much, there is a new directory in Vim's runtime called <code>pack</code> under which you can put whole third-party plugins, each in their own directory, which is basically what you are trying and failing to do in <code>plugin/</code>. So, instead of the layout above, you would have:
<pre><code>&quot; one directory for plugin `foo`
pack/&lt;whatever&gt;/start/foo/plugin/foo.vim
 indent/foo.vim
 syntax/foo.vim
&quot; and one directory for plugin `bar`
pack/&lt;whatever&gt;/start/bar/indent/bar.vim
 syntax/bar.vim
</code></pre>
In a normal setup for a normal user, that <code>pack</code> directory should be created under <code>$HOME/.vim/</code>. In this specific case, the right place is almost certainly <code>$VIM/vimfiles/</code>. The exact value of <code>$VIM</code> depends on many things so you will have to ask Vim where it is with:
<pre><code>:echo $VIM
</code></pre>
and adjust your installation script accordingly.
<hr />
I am not sure about the benefits of containerizing Vim, though.

blocks|key|95678|text|既然我不能发表评论，我就把这些留在这里。您可以看到其他人是如何在最流行的vim发行版SpaceVim中这样做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95679|SpaceVim码头安装|ordered-list-item|offset|length|95680|SpaceVim码头回购|95681|其他简单例子|95682|entityMap|0|LINK|mutability|MUTABLE|url|https://spacevim.org/quick-start-guide/#run-in-docker|1|https://github.com/SpaceVim/SpaceVim/tree/master/docker|2|https://github.com/drvim/drvim^0|0|0|C|0|0|0|C|1|0|0|6|2|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]]|A|$]]|$1|G|3|H|5|D|7|11|8|@]|9|@$E|12|F|13|1|14]]|A|$]]|$1|I|3|J|5|D|7|15|8|@]|9|@$E|16|F|17|1|18]]|A|$]]|$1|K|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]|U|$5|N|O|P|A|$Q|V]]]]

Since I was not able to comment, I'll leave these here.
You can see how others do it in the most popular vim distribution SpaceVim.
<ol>
<li><a href="https://spacevim.org/quick-start-guide/#run-in-docker" rel="nofollow noreferrer">SpaceVim Docker install</a></li>
<li><a href="https://github.com/SpaceVim/SpaceVim/tree/master/docker" rel="nofollow noreferrer">SpaceVim Docker repo</a></li>
<li><a href="https://github.com/drvim/drvim" rel="nofollow noreferrer">other simple example</a></li>
</ol>

blocks|key|1186078|text|尝试以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1186079|sudo+docker+run+-it+amine2029/vim-plug|code-block|syntax|javascript|1186080|我使用这个Dockerfile构建它：|1186081|FROM+ubuntu:18.04
RUN+apt-get+update+-yq+\
++++&&+apt-get+install+curl+-yq+\
++++&&+apt-get+install+-yq+vim+git+
RUN+curl+-fLo+~/.vim/autoload/plug.vim+--create-dirs+\
++++https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim+

ADD+vimrc+/root/.vimrc

RUN+vim+-E+-s+-u+"$HOME/.vimrc"+%2BPlugInstall+%2Bqall|1186082|这个'vimrc‘文件需要在构建目录中(在这里添加更多插件)：|1186083|call+plug#begin()
+Plug+'tomlion/vim-solidity'
call+plug#end()|1186084|然后建造：|1186085|sudo+docker+build+-t+vim-plug+.|1186086|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

try this command:
<pre><code>sudo docker run -it amine2029/vim-plug
</code></pre>
I build it using this Dockerfile:
<pre><code>FROM ubuntu:18.04
RUN apt-get update -yq \
 &amp;&amp; apt-get install curl -yq \
 &amp;&amp; apt-get install -yq vim git 
RUN curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
 https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim 

ADD vimrc /root/.vimrc

RUN vim -E -s -u &quot;$HOME/.vimrc&quot; +PlugInstall +qall
</code></pre>
This 'vimrc' file need to be in the building directory (add more plugins here):
<pre><code>call plug#begin()
 Plug 'tomlion/vim-solidity'
call plug#end()
</code></pre>
then to build:
<pre><code>sudo docker build -t vim-plug .
</code></pre>

I am trying to containerize vim along with the plugins. I am using singularity containers. The most important plugin is <a href="https://github.com/ycm-core/YouCompleteMe" rel="nofollow noreferrer">youcompleteme</a>. My approach to containerizing the plugins is to install vim and clone all the plugins to <code>/etc/vim/plugin</code> and compile youcompleteme during the build.
Once the image is built, I launch vim with the modified <code>runtimepath (rtp)</code> that points to /<code>etc/vim</code>:
<blockquote>
singularity run vim_image.sif vim --cmd 'set rtp^=/etc/vim'
</blockquote>
But, vim is failing to load the plugins. I am getting errors like:
<blockquote>
Error detected while processing
/etc/vim/plugin/sonokai/autoload/airline/themes/sonokai.vim: line 
10: E117: Unknown function: sonokai#get_configuration line 11: E121:
Undefined variable: s:configuration E116: Invalid arguments for
function sonokai#get_palette(s:configuration.style,
s:configuration.colors_override)
...
</blockquote>
I expect vim to load any plugins inside <code>/etc/vim/plugin</code> without any issues. I am stuck on this. Any suggestions are welcome.

Containerizing vim with plugins

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正试图将vim和插件一起封装起来。我在使用奇点容器。最重要的插件是。我封装插件的方法是安装vim并将所有插件克隆到/etc/vim/plugin中，并在构建过程中编译youcompleteme。生成映像后，使用指向/etc/vim的修改后的runtimepath (rtp)启动vim奇点运行vim_image.sif...

问用插件封装vim
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用插件封装vimEN