I've compiled gvim on solaris before. It is something for which I have to schedule a lot of time. However, many of the problems I had may have stemmed from the fact that I only had a user account, and if I recall correctly, this may have caused problems with installation of prerequisite software.
I looked at your installation instructions, and I have to admit that it's still something for me to jump into when I have lots of time. I'll live with cygwin installs of gvim for the time being. Thank you for your advice. On Jan 18, 12:22 am, Tony Mechelynck <[email protected]> wrote: > On 18/01/10 05:04, AndyHancock wrote: > > > > > 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. > > I mean you can have them on the same machine but (in most cases) it's > easier to use Windows-native with native and Cygwin with Cygwin. It is > possible to mix them, but beware of paths (see man cygpath), and I've > never succeeded to get Cygwin X11 running satisfactorily, so for me > Cygwin is more like a Windows emulator "text-only" Unix environment > similar to init runlevel 3 on Linux -- let's say Wine in reverse (where > Wine is a WIN-dows E-mulator running on Linux). > > > > > 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). > > I avoid Cygwin install of gvim. When I was on Windows I had three Vim > builds: Windows gvim.exe (GUI), Windows vim.exe (for use in cmd.exe, > either windowed xterm-like or full-screen text-only terminal) and Cygwin > /bin/vim compiled by Cygwin, and thus always slightly out-of-date > compared to my own "fully patched" builds (for use in bash terminal). > > The Cygwin cross-compile is already done by Steve Hall who periodically > generates a Windows installer,http://sourceforge.net/projects/cream/files/You > *may* compile Vim for > yourself (it isn't very difficult: the "make" program does most of the > work) if you want a different choice of features, but you don't *have* > to. See (for Windows) my HowTo > pagehttp://users.skynet.be/antoine.mechelynck/vim/compile.htm-- even if you > don't want to do it, you may have a look at it (and if there's anything > you don't understand, I'd like to know about it). > > Best regards, > Tony. > -- > hundred-and-one symptoms of being an internet addict: > 243. You unsuccessfully try to download a pizza fromwww.dominos.com. -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
