本文介绍了在多台机器上处理vim插件的最佳方式是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在多台机器上处理它们的最佳方法是什么?我看到了类似git子模块的东西。还有病原体。一些vim插件甚至不支持病原体。我在多台机器上工作。另外在Arch-Linux中,你可以在官方回购中找到大部分插件。那么从那里安装好?



最好的方法是什么? 您已经找到并列举了所有流行的方法;您可以选择最适合您的特定环境和工作风格的选择。感谢Vim是如此巨大的可配置性,并与各种工具很好地集成在一起。不要期望一个可以简单遵循的权威答案。使用你自己的直觉(并且一旦你对你的方法感到满意,就和其他人一样分享你的发现)。



就我个人而言,我已经配置了Vim在Windows上也可以使用〜/ .vim 而不是〜/ vimfiles

 在Windows上,也可以使用〜/ .vim而不是〜/ vimfiles;这使得跨异构系统的同步
更容易。
如果有('win32')|| ('win64')
set runtimepath = $ HOME / .vim,$ VIM / vimfiles,$ VIMRUNTIME,$ VIM / vimfiles / after,$ HOME / .vim / after
endif

我主要使用,以在大约10个不同系统中分发我的点文件。


What is the best way to deal with them on multiple machines? I saw something like git submodules. And there is pathogen. Some vim plugins even doesn't support pathogen. I work on multiple machines. Also in Arch-Linux you can find most plugins in the official repos. So is it good to install from there?

What is the best way?

解决方案

You've already found and enumerated all the popular approaches; it's up to you to pick one that best matches your particular environment and style of work. Be thankful that Vim is so immensely configurable and integrates well with a variety of tools. Don't expect an authoritative answer that you can simply follow. Use your own intuition (and share your findings like others (e.g. in a blog post) once you're satisfied with your approach).

Personally, I've configured Vim to also use ~/.vim instead of ~/vimfiles on Windows:

" On Windows, also use ~/.vim instead of ~/vimfiles; this makes synchronization
" across (heterogeneous) systems easier.
if has('win32') || has('win64')
    set runtimepath=$HOME/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,$HOME/.vim/after
endif

I mostly use the Unison File Synchronizer to distribute my dotfiles among about 10 different systems.

这篇关于在多台机器上处理vim插件的最佳方式是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-16 08:13