On Jan 17, 9:49 pm, Tony Mechelynck <[email protected]> wrote: > IMHO it's easier to keep native-Windows (with gvim GUI for Windows, > and/or Vim for Windows running in cmd.exe) and Cygwin (with Vim for > Cygwin running in bash) apart from each other. If you need to copy-paste > between Vim and other Windows applications, I recommend using gvim for > Windows (which can be built in Cygwin as a kind of "cross-compile", but > doesn't need Cygwin to run), which natively "understands" the Windows > clipboard as "* or "+. Now YMMV.
When you say keep them separate, do you mean not have them no the same machine? I have kept them together on the same machine before, though it was in a previous laptop. However, they were completely different apps. On was installed under the cygwin tree while the other used the Windows installer. I was able to use the same vimrc. Unfortunately, the "!" command in the Windows version didn't shell out to bash. I might have been able to force it to shell out to bash at some point through some through some abomination of vimrc scripting, but it was far from robust so I didn't bother keeping bother keeping track of how it was done. Anyway, I was trying avoid doing a Windows installation of gvim because it seemed excessive to have two gvim's on the same system. However, I may yet go back on that decision simply because of the inconvenience of having to transfer text to Notepad and write it to a file before sic'ing gvim onto it. I will likely not do the cygwin cross-compile route simply for lack of time to become technically competent enough (and because the windows installer is readily available).
-- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
