@jKey’s method is feasible. gvim will try to load plug-ins, documents and other files in rtp, which is the runtimepath, so you only need to add a path to rtp
Actually, I would like to recommend a vim extension called vundle https://github.com/gmarik/vundle. It will create a separate folder for each different plug-in. The principle is achieved through the management of rtp. The folder is separated to facilitate deletion of plug-ins later.
Because he installs the plug-in through git+github, it is also very convenient to update/install the plug-in. It solves the difficult problem of gvim plug-in management very well.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Try this
@jKey’s method is feasible. gvim will try to load plug-ins, documents and other files in rtp, which is the runtimepath, so you only need to add a path to rtp
Actually, I would like to recommend a vim extension called vundle https://github.com/gmarik/vundle. It will create a separate folder for each different plug-in. The principle is achieved through the management of rtp. The folder is separated to facilitate deletion of plug-ins later.
Because he installs the plug-in through git+github, it is also very convenient to update/install the plug-in. It solves the difficult problem of gvim plug-in management very well.
Old way