Installing pathogen vim plugin on Windows - windows

I was going to install the pathogen plugin in GVIM for windows but the instructions say to install in the \vimfiles\autoload folder which I don't have. How would I install pathogen?

If it does not exist you can simply create the folder.
Place pathogen.vim inside ...\vim\vimfiles\autoload and you should be good to go.
Bundles go into ...\vim\vimfiles\bundle

You can read this document..
GVim for Windows
Or
You can go to this link
Vim and Pathogen for Windows

You need to create the folders if absent.
Open Vim, type ":e $VIM" and you'll find your vim directory where the vimfiles folder is. (if you did not know that already)
Also, please see gvim pathogen issues
for more help.

Related

How to change color themes in Vim for Windows 7

I'm a Vim beginner and I would like to change the color theme to a more appropriate one for C programming (I'm using Windows 7, Vim 8.2). After looking for a while, I found the Dracula theme https://draculatheme.com/vim/ but I'm having some trouble installing it.
First of all, I could not locate the .vim folder as the instruction says. I have C:\Program Files (x86)\Vim with a _vimrc file, vimfile and vim82 folder. I tried anyway to create the themes and start folder in the pack folder located in \vim82, but when I try to git clone it, I get this message: "fatal: could not create work tree dir 'dracula': Permission denied".
Any help?
EDIT: after running the cmd.exe as administrator, I was able to clone the repository. It doesn't work though. I also tried :echo $HOME, it indicates a vimfile folder in C:\Users\XXXX. I tried the same here but with no results.
In windows, vimfiles folder can be located in $HOME\vimfiles or in $VIM\vimfiles.
* More information: :h vimfiles
To install a colorscheme manually (without using a plugin manager), you need to download all its files https://github.com/dracula/vim, then copy all files in these directories (after, autoload, colors, and doc) to directories of same names inside vimfiles folders.
To use the colorscheme, place this in your _vimrc:
:colorscheme dracula

get vim working in mobaxterm

I have installed gvim and vim in mobaxterm 8 (using apt-get and mobapt respectively), and can't get either to work. nano works fine.
When I run the program, the cursor moves to a new line in the terminal but nothing happens.
I have also tried creating a .vimrc. Does anyone have any ideas? Thanks.
I installed the latest version of MobaXterm as up today which is 9.1 (http://mobaxterm.mobatek.net/download-home-edition.html) and the list of bug fixes includes the freezing problem you are are talking about. It works for me now and I no longer see that issue. The only thing is that after the installation is completed you need to download the CygUtils plugin and copy it to the same folder where the MobaXterm executable is located and then restart the application. It seems overall more stable now. Hope that helps.
I am using V9.4 which already has the vim. To configure the environment for your vim you may creat a .vimrc file in your home directory (go to the directory using cd command only).

How to install plugin for MobaXterm?

I need a terminal that will support svn on windows and I found that MobaXterm is one of them. However going to their plugin installation page which says:
To install these plugins, just download them and put them in the same directory than the MobaXterm executable.
So I downloaded it and put it in the file
C:\Program Files (x86)\Mobatek\MobaXterm Personal Edition however I still get the error message
Sorry: Svn is not included in this version of MobaXterm.
You can check online if you find a Svn plugin for MobaXterm
by ctrl+clicking here: http://mobaxterm.mobatek.net .
If you need a custom version of MobaXterm that includes Svn,
do not hesitate to ask us for a quotation: mailto:contact#mobatek.net .
Does anyone have experience with this software or recommended a terminal that can support svn in windows?
You need to go into the C:\Program Files (x86)\Mobatek\MobaXterm Personal Edition or whichever edition you have and place the plugin there. Restart MobaXterm and it should work.
I normally collect all the plugins which I require from http://mobaxterm.mobatek.net/plugins.html
Once the .mxt3 files are getting downloaded, I moved them to the installed folder where the MobaXterm_.exe is there.
After restarting MobaXterm, this will work like a champ.
Hope if this solves your issue faster.
Start MobaXterm terminal.
Type MobApt or apt-get. This will open MobApt package manager.
Once in the package manager, you have a variety of tools/commands that you can install by simply selecting and pressing Install/Update.
i know the question is old. but you should put the plugin into your home.
if you check the setting you see this is the home directory
%CurrentDrive%:\Users\USERNAME\Documents\MobaXterm\home
witch is :
C:\Users\USERNAME\Documents\MobaXterm\home -- or whatever drive that u installed windows
i just installed the python plugin and it works fine
In Mobaxterm simply type : apt-get install subversion
Usable just right after installation. No need to restart.
Same for git.
Change the name of the .mxt3 file (that you downloaded) to .zip
Extract the files, get the .exe files you want from the bin folder
from the files you just extracted, and add them to the slash/bin
folder of the Mobaxterm (where there are more .exe files)
Restart
In order to finish your plugin installation, you need to restart MobaXterm. After restarting, type "svn" in the terminal and it should work.
Try run the command:
#unalias svn
When I saw $PATH and looked into its directories, there was no git.exe.
I downloaded git.mxt3 and put in program files (86) folder and restarted mobaterm.
After restart I can see a file named git.exe in my /bin folder. I am using Win7 (64 bit) and mobaXterm personal Edition v7.1 installed using windows installer (not portable )
MobaXterm already has a 'Packages' button where you can search for plugins and download them. You don't need to go to github and other places to find the necessary files. Just using the built-in search feature under the 'Packages' option at the top of MobaXterm.

I can't find my MinGW shell after installing with GUI installer

I used Mingw_get_inst and installed the MinGW compiler suite following the instructions on the howto page. I used the GUI installer. I then changed the path to include C:\MingW; . When I go to Start menu -> all programs -> MingW the only file that exists inside of there is a uninstaller. The howto page says a shell should be there... can someone help me get this working?
Howto page on Mingw.org: http://www.mingw.org/wiki/Getting_Started
simply you could run it from the following batch file:
e.g. C:\MinGW\msys\1.0\msys.bat (if you installed your mingw in c drive)
for more info. about mysys, check this
Look at the install logs for your Mingw.
I have 2 bin dirs in my (single) installation of Mingw
C:\MinGW\msys\1.0\bin
and
C:\MinGW\bin
A lot has changed about Mingw in the last 2-3 years and I think some documentation you might find easily via google is out-of-date.
Try asking for help at mingw mail groups via Nabble (very easy to use)
IHTH
Adding the shell link is easy if you have MSYS installed.
Open your Start menu and right-click on "All Program" and choose either "Open" or "Open All Users" depending on which you want to set the shortcut for. Open the MinGW folder if it already exists, or create it (or an MSYS folder, as you wish) if it does not.
Open another Explorer window and navigate to your MSYS folder, in the default installation this is C:\MinGW\msys\1.0
Right-drag msys.bat from the MSYS explorer window to the start menu explorer window. Choose "Create shortcut" when prompted as to what you wish to do. Optionally, you may want to change the shortcut to use one of the MSYS icons from the MSYS folder.
According to older MSYS documentation, the shortcut should be set to start in the MSYS bin folder, in the default installation this is C:\MinGW\msys\1.0\bin. I'm not certain of what happens if you don't do this; the shell opens either way.
Et voilĂ ! You now have a shell link for MSYS in your Start menu.
If you didn't have the shortcut, the other postinstall bits may not have run either. The easy way to check this is to look in C:\MinGW\msys\1.0\etc (or the appropriate path for your installation). If there is an fstab file, then the postinstall bits ran appropriately. If not, then go to C:\MinGW\msys\1.0\postinstall and run pi.bat. This will make the mingw folder available from the msys shell. Things won't work right without doing this.
Update from March 2018: The MSYS postinstall is now a Lua script, and it won't create a shortcut by default. Best I can tell, you now must do so manually in all cases.
Look for the postinstall directory, run the batch file pi.bat in there and
answer the file path questions with the correct case sensitivity.
Then gcc is found.
CNTRL-SHIFT click and drag the msys shortcut onto the desktop.
This fixes it.
Pity the installation script is broken...
Go to your windows search and go to Apps and Features and then search for it, you can find the file location and then you can probably see docs and other files :)

How can I test my vim plugin?

Hi guys : I recently (accidentally) removed all folders/files from my .vim folder in mac os x (home directory).
I am trying to add in the Clojure Vim plugin (VimClojure) - its simply a folder which you are supposed to "drop into .vim/plugins".
I have added it, but I don't see any changes to the syntax highlighting when I launch vim. I'm not sure wether vim "sees" the plugin or not.
I'm on OS X .
Any ideas on how to debug the plugin ? In particular
1) How does VIM look for plugins ?
2) Are there files which need to be in $HOME/.vim/ ?
3) Is it sufficient to simply dump the unzip a new plugin file into $HOME/.vim/plugins when installing a standard vim plugin ?
Thanks
About debugging: in order to see whether vim has loaded your plugin you can use :scriptnames and also breakadd file /path/to/your/plugin (or breakadd file *your_plugin_name.vim: I never used absolute paths so I do not know what breakadd will do in this case). Other questions:
Described in :h initialization, precisely :h load-plugins.
Vim does not need any files at all (except vim executable, used shared libraries, dynamic linker and the kernel of course).
Follow installation instructions. Normally plugins are either extracted to ~/.vim or distributed as a singe file that should go to either ~/.vim/plugin (no s!), ~/.vim/colors, ~/.vim/ftplugin or such. I guess you should try to extract it to ~/.vim/plugin, but if archive contains some special directories like plugin/, ftplugin/, colors/, after/ (see /usr/share/vim/vim73 for a list) it is likely that it should go to ~/.vim. Also consider using vim-addon-manager, if plugin was posted on vim.org VAM is likely to be able to install it.
A few points.
How does vim look for plugins? See :help startup so see where and when vim looks for files to load.
Not really. Anything there is just personal customization. Vim will run fine without a .vim folder.
That all depends on the plugin. It sounds to me like the VimClojure plugin may be a little misleading. Do you have a link to the source you are using?
In any case, the first step I always take when attempting to debug a script is check the output of :scriptnames. This command will show you what scripts vim has loaded for the current session. If you see none of the files shipped with VimClojure, you probably made a mistake during the installation.
Another tip is that you really should look in to using a plugin manager such as vundle or vim-addon-manager, or at least the runtimepath manager pathogen. This seems to be the way of the future for vim configuration these days and it makes installing and managing plugins much easier. They also help to keep your .vim folder clean and organized.
The VimClojure directory should either be extraction on top of your .vim folder, or in a bundle folder if your using something like pathogen (which you should!). If you're starting from scratch, consider starting with vimclojure-easy (not to toot my own horn) which is a basic, full install of VimClojure with instructions.

Resources