On Sat, 2007-12-22 at 10:35 +0000, Vance Briggs wrote:
> Hi all,
> This is my first post to the mailing list.
> I use Cream on both Linux and Windows and am attempting to get it
> running on OS X (10.5 Leopard).
Great, we occasionally see interest in this here, but I am Mac-free
and unable to do it without help.
> I am using:
> Vim 7.0.224 for OS X downloaded from the official VIM site the
> output of vim -h gives:
> VIM - Vi IMproved 7.0 (2006 May 7, compiled Mar 30 2007 12:57:49)
Should be sufficient. The latest at this moment is 7.1.175, although
none of these revs indicate new features, only bugfixes.
> I have installed Cream using the command line install method
> then installing Cream:
> INSTALL.sh /usr/local/bin
You want to put cream in the vim program folder, wherever :echo
$VIMRUNTIME indicates. Cream is not an app in itself, only a set of
runtime scripts for Vim.
> When I try to run Cream from the command line vim complains that is
> doesn't support the option --servername (Which I believe is the
> cause of the problem...)
> If I remove the --servername "CREAM" from the cream shell script
> then it goes further, a vim window opens, but dies shortly after.
Cream isn't recommended for terminal Vim, only gVim. There are too
many issues with shells that prevent it from functioning properly at
the terminal version.
> If I start cream from inside a running gvim session then I get the
> following problems:
> :source $VIMRUNTIME/cream/creamrc
> vim sloooowly starts cream...
Per the above issue with Cream install location and $VIMRUNTIME, maybe
because they are not coordinated?
> You can see the menus being recreated, then it complains about a
> script error:
> Error etected while processing function Cream_statusline_autowrapOFF:
> line 5:
> E121: Undefined variable: g:CREAM_AUTOWRAP_WIDTH
> pressing return then gives a second error that is effectively the
> same problem.
Hmm, maybe fix Cream_statusline_autowrapOFF() in cream-statusline.vim
to read like:
" use global, actual width is 0
return "auto " . g:CREAM_AUTOWRAP_WIDTH
return "auto " . &textwidth
> However, continuing through does seem to start cream.
> It either ignores the setting of expert mode in the ~/.cream/cream-
> conf.vim or the mapping of the escape key is not correct, but this
> is a minor problem at the monent.
Agreed, I'd like to make sure it works to the defaults without any
cream-conf or cream-user being involved.
> I can get into vim mode using <ctrl>-L
> When I issue the command:
> :doautoall VimEnter
> the window effectively closes, giving me the option to save any
> modified documents.
Sourcing creamrc should take care of all this, I wouldn't re-trigger
autocmds since there are a whole host of inter-dependencies that may
be confused if certain variables already exist.
> I think this is related to that fact that cream tries to start a
> named server and move all documents across to a remote instance of
> the named server, but somehow this isn't supported in the OS X
> version of VIM.
> As an aside on OS X there is an additional application installed
> that gvim.app as opposed to vim.app. If I find the executable it
> doesn't complain about not supporting the --servername option, but
> it doesn't respond to -h either, so not sure whether this would help
Definitely use gvim.app. I'm not sure why the "-h" wouldn't work, but
that shouldn't affect Cream.
> Any help or pointers of what to try next would be greatly
Let me know if any of the above helped. I'd really like to get Cream
working on OS X, at least to the point that Vim will support it. I'm
not sure if Vim can even utilize the GUI to the extent it does on
Windows and GNOME/Linux, but with your (and other's) assistance we
should be able to avoid the startup issues you are currently seeing.
Steve Hall [ digitect dancingpaper com ]
:: Cream... usability for Vim