>> AndyHancock wrote: >>> This problem dogged me for many years, and I finally hunkered down >>> to chase it down. >>> >>> Here is the solution that I found works for me: >>> >>> "set shell=c:\cygwin\bin\bash.exe\ -i >>> "Won't always find ~/.bashrc cuz depending on how vim is >>> "launched, ~ doesn't always resolve to c:/cygwin/home/$USERNAME
> I don't know if setting the environment variable SHELL would propagate > its value into the vim option "shell". However, even if it did, I > would feel more comfortable with the command in my code because just > setting the shell alone left the rc file un-executed, even with the > interactive flag was provided as part of the "shell" option (which is > suppose to cause the rc file to run). It's all kind of foggy to me > now, but I believe that one of the possible causes was that $HOME was > being set to different things depending on how vim was invoked. So it > wasn't finding the rc file in many cases. I never tried to shelling using cygwin bash on Windows GVim. I will give a shot. In respect to '~' to be recognized as $HOME you will need to create an environment variable, in Windows, targeting that path. Be prepared that if you have any other cross platform software it probably will use that %HOME% path to write temporary and configuration specific files (Inkscape, GIMP, Dia, etc.). The best thing about this configuration is that both Windows Vim/Gvim and cygwin vim uses the same user runtime path (~/.vim) with save me for synchronizing plugins, syntaxes, colors, etc. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
