To summarize, I haven't been able to get it to run. Therefore I am suggesting two solutions below.
The Mac port of gvim was withdrawn at some point in the past. MacVim is typically used. MacVim is a fully functional version of gvim. It has the added benefit of being compatible with the Mac clipboard, fully supporting the Mac App functionality, and looking truly lovely on a Retina display. Unfortunately MacVim does not accept the normal gvim startup arguments. It is normally launched as a graphical app within Mac OS X. You can pass startup arguments to it with the mac-unix open command, however MacVim is either not expecting them, or is missing some extra step to support them. ***This prevents Cream from running on a Mac.*** Two separate but complementary things can be done to address this issue. 1. (Out of scope for the Cream project — in scope for the MacVim project). Someone can fix MacVim to accept command line arguments, and hopefully make a “gvim” script alias that will pass that information along to MacVim. 2. (In scope for Cream) Someone can produce a patch to the vim scripts that causes Cream to be used without any gvim command line arguments. This would consist of hard-coding the information that the cream startup command normally passes along to gvim. It would prevent gvim from being used without Cream, so it should be done in a way that makes it easy for someone to go in and disable it, by commenting out a single line for example. Especially if MacVim has further incompatibilities. If someone knows of a way to patch the vim scripts as mentioned in item 2 above, then I would be excited to try it out. Has anyone done that before? Thanks, Erik
------------------------------------------------------------------------------
_______________________________________________ cream-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cream-general
