Detailed steps for using vim + python to build your own IDE plug-in

This article describes how to use vim + python to build your own IDE plug-in. Today, my colleague suddenly told me that his editor sublime3 caused a sudden lag in the notebook and saw that the memory was 30 GB, his notebook only had 8 GB of memory in total, and suspected it was a memory leak. he decisively switched back to the original PyCharm. Because I also used PyCharm to learn python and knew that its memory usage was above 1 GB. when I heard this message, I decided to switch back to vim, which I had always used, after all, the "God of editors" is not a waste of virtual names.

The so-called build is actually to find some plug-ins suitable for you. first, I will briefly summarize some plug-ins that I have tested. First, I would like to explain that the several plug-ins mentioned here are very powerful and well-known, but the so-called suitable plug-ins are the best. the shortcomings mentioned in this article are just a personal experience, not applicable to all users. The sharing is just a reference for your selection. Thank you ~

1. vim plug-in manager

Vim-pathogen VS Vundle. vim:

Both plug-ins are vim artifacts used for vim plug-in management. After the pathogen configuration is complete, you only need to put the vim plug-in you downloaded ~ /. Vim/bundle (or custom) directory, and vundel needs to change the vimrc file each time. However, the convenience of vundel is that after the vimrc file is changed, it can be directly used in vim: pluginInstall to install the plug-in with one click. The principle is to automatically download the plug-in from GitHub and other sources.

Here I chose vundle, because we can see from the configuration file which plug-ins I have installed at a glance, and comment out the plug-ins that are not needed. For example, the plug-in is the plug-in I installed, which is clear at a glance.

In the end, what suits you is the best.

The above describes how to use vim + python to build your own IDE plug-in. For more information, see other related articles in the first PHP community!