Thread: [cream] Trying to get Cream running on Mac OS X
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Vance B. <va...@ax...> - 2007-12-22 10:35:29
|
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). 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) I have installed Cream using the command line install method setting : export VIMRUNTIME="/Applications/Vim.app/Contents/Resources/vim/runtime" then installing Cream: INSTALL.sh /usr/local/bin 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. If I start cream from inside a running gvim session then I get the following problems: :source $VIMRUNTIME/cream/creamrc vim sloooowly starts cream... 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. 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. 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. 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 either... Any help or pointers of what to try next would be greatly appreciated. Thanks Vance |
From: Steve H. <dig...@da...> - 2007-12-23 01:32:31
|
On Sat, 2007-12-22 at 10:35 +0000, Vance Briggs wrote: > > Hi all, > > This is my first post to the mailing list. Welcome. > 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 > setting: > > export VIMRUNTIME="/Applications/Vim.app/Contents/Resources/vim/runtime" > > 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: function! Cream_statusline_autowrapOFF() if &textwidth return "" else if exists("g:CREAM_AUTOWRAP_WIDTH") " use global, actual width is 0 return "auto " . g:CREAM_AUTOWRAP_WIDTH else return "auto " . &textwidth endif endif endfunction > 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 > either... 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 > appreciated. 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 :: http://cream.sourceforge.net |
From: Wolfgang H. <wo...@co...> - 2007-12-23 15:27:38
|
Hello there, >> :source $VIMRUNTIME/cream/creamrc >> Error etected while processing function Cream_statusline_autowrapOFF: >> line 5: >> E121: Undefined variable: g:CREAM_AUTOWRAP_WIDTH > Hmm, maybe fix Cream_statusline_autowrapOFF() in cream-statusline.vim > to read like: Thanks Steve, this fixed this (minor) problem. However, it still won't work as expected: - The MacVim version of Vim on OS X loses all of its icons and menus after :source'ing creamrc in. - The DarwinPorts version of Vim (compiles gvim from its sources) behaves rather slow on the :source command, just as Vance described. Afterwards, the menus are a big mess. Most menu entries are not there at all; this appears to be somehow related to those menu entries for which keyboard shortcuts are defined, and those with submenus. For example, Settings -> Preferences is missing completely. This leaves me in a state where the statusline and other look & feel is already creamish, but without all the menus, using it becomes harder than usual. :-) I know it's hard to debug without a Mac around. Maybe I can arrange some remote access to one next year. Cheers, Wolfgang |
From: Steve H. <dig...@da...> - 2007-12-27 00:56:38
|
On Sun, 2007-12-23 at 16:27 +0100, Wolfgang Hommel wrote: > > Thanks Steve, this fixed this (minor) problem. However, it still > won't work as expected: > > - The MacVim version of Vim on OS X loses all of its icons and menus > after :source'ing creamrc in. > > - The DarwinPorts version of Vim (compiles gvim from its sources) > behaves rather slow on the :source command, just as Vance > described. Afterwards, the menus are a big mess. Most menu entries > are not there at all; this appears to be somehow related to those > menu entries for which keyboard shortcuts are defined, and those > with submenus. For example, Settings -> Preferences is missing > completely. There must be some pretty big bugs in the Mac port of gvim. Cream isn't doing anything that isn't documented. The only question is there something minor we can do to fix it? Is it possible that some libraries that might be missing? > I know it's hard to debug without a Mac around. Maybe I can arrange > some remote access to one next year. That might work for a night or two. Long term though, we'll need a native user, someone with vim background to fix bugs and spot areas for improvement. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Vance B. <va...@ax...> - 2008-01-03 20:25:54
|
Thanks for your responses so far. I have not done too much over Christmas, but will continue to have a look at this. I think that the Mac version of vim is fundamentally different enough to mean that Cream will have difficulty running on it. I am currently using Benji Fisher's version compiled for OS X and it gives: Vances-Mac-Pro:src vance$ gvim --version Vances-Mac-Pro:src vance$ VIM - Vi IMproved 7.0 (2006 May 7, compiled Mar 30 2007 12:57:49) MacOS X (unix) version Included patches: 1-224 Modified by Benji Fisher Compiled by Benji Fisher <http://macvim.org/OSX> Huge version with Carbon GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent -clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() -gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile +python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/Applications/Vim.app/Contents/Resources/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MAC -fno-common -fpascal-strings -Wall -Wno-unknown-pragmas -mdynamic-no-pic -pipe -I. -Iproto -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/FlatCarbon -g -O -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -g -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -I/usr/local/include -I/System/Library/Perl/5.8.6/darwin-thread-multi-2level/CORE -I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3 -I/System/Library/Frameworks/Tcl.framework/Headers -D_REENTRANT=1 -D_THREAD_SAFE=1 -I/usr/lib/ruby/1.8/universal-darwin8.0 Linking: gcc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -o Vim -framework Carbon -lncurses -liconv -L/usr/local/lib /System/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DynaLoader/DynaLoader.a -L/System/Library/Perl/5.8.6/darwin-thread-multi-2level/CORE -lperl -lm -lc -framework Python -framework Tcl -framework CoreFoundation -lruby -lobjc Of note is the lack of clientserver feature, which Cream uses. I think that this is the fundamental reason whi I can't start Cream from the command line and the reason it shuts down when I do a :doautoall VimEnter I will attempt to build vim from the sources to see whether I can get a version with clientserver enabled. I will keep you updated, but would welcome any ideas from the more knowledgeable community. Vance On 27/12/2007, Steve Hall <dig...@da...> wrote: > On Sun, 2007-12-23 at 16:27 +0100, Wolfgang Hommel wrote: > > > > Thanks Steve, this fixed this (minor) problem. However, it still > > won't work as expected: > > > > - The MacVim version of Vim on OS X loses all of its icons and menus > > after :source'ing creamrc in. > > > > - The DarwinPorts version of Vim (compiles gvim from its sources) > > behaves rather slow on the :source command, just as Vance > > described. Afterwards, the menus are a big mess. Most menu entries > > are not there at all; this appears to be somehow related to those > > menu entries for which keyboard shortcuts are defined, and those > > with submenus. For example, Settings -> Preferences is missing > > completely. > > There must be some pretty big bugs in the Mac port of gvim. Cream > isn't doing anything that isn't documented. The only question is there > something minor we can do to fix it? Is it possible that some > libraries that might be missing? > > > I know it's hard to debug without a Mac around. Maybe I can arrange > > some remote access to one next year. > > That might work for a night or two. Long term though, we'll need a > native user, someone with vim background to fix bugs and spot areas > for improvement. > > > -- > Steve Hall [ digitect dancingpaper com ] > :: Cream... usability for Vim > :: http://cream.sourceforge.net > > > |
From: Steve H. <dig...@da...> - 2008-01-04 01:45:55
|
On Thu, 2008-01-03 at 20:25 +0000, Vance Briggs wrote: > > Thanks for your responses so far. I have not done too much over > Christmas, but will continue to have a look at this. > > I think that the Mac version of vim is fundamentally different > enough to mean that Cream will have difficulty running on it. I am > currently using Benji Fisher's version compiled for OS X and it > gives: > [...] > > Of note is the lack of clientserver feature, which Cream uses. I > think that this is the fundamental reason whi I can't start Cream > from the command line and the reason it shuts down when I do a > :doautoall VimEnter > > I will attempt to build vim from the sources to see whether I can > get a version with clientserver enabled. > > I will keep you updated, but would welcome any ideas from the more > knowledgeable community. The clientserver feature really isn't necessary in Cream/Vim except to support a single session/instance. You could disable the checking in cream-server to see what happens with only minor bugs: o New sessions of Vim will not merge with existing ones, the app will be running multiple times (which some users actually prefer) o Changes to the environment (namely the recent file list and changes to settings and preferences) will be remembered only from the session last closed. There is likely some pretty significant code work to be done on the Mac to get this working...I'm sure if you are able to fix it there will be quite a few users that would appreciate it. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Vance B. <va...@ax...> - 2008-01-04 23:13:11
|
I have now managed to get Cream to run on OS X with a few minor tweaks: Stopped the following functions from running: cream-server.vim - Cream_singleserver_init() cream-server.vim - Cream_singleserver() by inserting near the top of each function: if has("mac") return endif I also fixed the startup error that was complaining about a nonexistant variable (g:CREAM_AUTOWRAP_WIDTH). So the function now reads: cream-statusline.vim function! Cream_statusline_autowrapOFF() if &textwidth return "" else " use global, actual width is 0 if exists("g:CREAM_AUTOWRAP_WIDTH") return "auto " . g:CREAM_AUTOWRAP_WIDTH else return "" endif endif endfunction I can now start cream from the command line using the following: /Applications/Vim.app/Contents/MacOS/Vim -g -U NONE -u "\$VIMRUNTIME/cream/creamrc" and I get something resembling Cream ;-) There is still more to sort out as the backspace key doesn't work as it should in insert mode, although it does in gvim... In addition, Cream runs pretty slowly compared to gvim, especially when switching buffers. But at least I have some progress... Vance On 03/01/2008, Vance Briggs <va...@ax...> wrote: > Thanks for your responses so far. I have not done too much over > Christmas, but will continue to have a look at this. > > I think that the Mac version of vim is fundamentally different enough > to mean that Cream will have difficulty running on it. I am currently > using Benji Fisher's version compiled for OS X and it gives: > > Vances-Mac-Pro:src vance$ gvim --version > Vances-Mac-Pro:src vance$ VIM - Vi IMproved 7.0 (2006 May 7, compiled > Mar 30 2007 12:57:49) > MacOS X (unix) version > Included patches: 1-224 > Modified by Benji Fisher > Compiled by Benji Fisher <http://macvim.org/OSX> > Huge version with Carbon GUI. Features included (+) or not (-): > +arabic +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent > -clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments > +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic > +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path > +folding -footer +fork() -gettext -hangul_input +iconv +insert_expand +jumplist > +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu > +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm > -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme > -netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile > +python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent > -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static > -tag_any_white +tcl +terminfo +termresponse +textobjects +title -toolbar > +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace > +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp > -xterm_clipboard -xterm_save > system vimrc file: "$VIM/vimrc" > user vimrc file: "$HOME/.vimrc" > user exrc file: "$HOME/.exrc" > system gvimrc file: "$VIM/gvimrc" > user gvimrc file: "$HOME/.gvimrc" > system menu file: "$VIMRUNTIME/menu.vim" > fall-back for $VIM: "/Applications/Vim.app/Contents/Resources/vim" > Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MAC > -fno-common -fpascal-strings -Wall -Wno-unknown-pragmas > -mdynamic-no-pic -pipe -I. -Iproto -DMACOS_X_UNIX -no-cpp-precomp > -I/Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/FlatCarbon -g -O > -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -g > -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing > -I/usr/local/include > -I/System/Library/Perl/5.8.6/darwin-thread-multi-2level/CORE > -I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3 > -I/System/Library/Frameworks/Tcl.framework/Headers -D_REENTRANT=1 > -D_THREAD_SAFE=1 -I/usr/lib/ruby/1.8/universal-darwin8.0 > Linking: gcc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 > -arch ppc -o Vim -framework Carbon -lncurses -liconv > -L/usr/local/lib > /System/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DynaLoader/DynaLoader.a > -L/System/Library/Perl/5.8.6/darwin-thread-multi-2level/CORE -lperl > -lm -lc -framework Python -framework Tcl -framework CoreFoundation > -lruby -lobjc > > Of note is the lack of clientserver feature, which Cream uses. I > think that this is the fundamental reason whi I can't start Cream from > the command line and the reason it shuts down when I do a > :doautoall VimEnter > > I will attempt to build vim from the sources to see whether I can get > a version with clientserver enabled. > > I will keep you updated, but would welcome any ideas from the more > knowledgeable community. > > Vance > > On 27/12/2007, Steve Hall <dig...@da...> wrote: > > On Sun, 2007-12-23 at 16:27 +0100, Wolfgang Hommel wrote: > > > > > > Thanks Steve, this fixed this (minor) problem. However, it still > > > won't work as expected: > > > > > > - The MacVim version of Vim on OS X loses all of its icons and menus > > > after :source'ing creamrc in. > > > > > > - The DarwinPorts version of Vim (compiles gvim from its sources) > > > behaves rather slow on the :source command, just as Vance > > > described. Afterwards, the menus are a big mess. Most menu entries > > > are not there at all; this appears to be somehow related to those > > > menu entries for which keyboard shortcuts are defined, and those > > > with submenus. For example, Settings -> Preferences is missing > > > completely. > > > > There must be some pretty big bugs in the Mac port of gvim. Cream > > isn't doing anything that isn't documented. The only question is there > > something minor we can do to fix it? Is it possible that some > > libraries that might be missing? > > > > > I know it's hard to debug without a Mac around. Maybe I can arrange > > > some remote access to one next year. > > > > That might work for a night or two. Long term though, we'll need a > > native user, someone with vim background to fix bugs and spot areas > > for improvement. > > > > > > -- > > Steve Hall [ digitect dancingpaper com ] > > :: Cream... usability for Vim > > :: http://cream.sourceforge.net > > > > > > > |
From: Wolfgang H. <wo...@co...> - 2008-02-03 10:43:58
|
> - The MacVim version of Vim on OS X loses all of its icons and menus > after :source'ing creamrc in. > - The DarwinPorts version of Vim (compiles gvim from its sources) > behaves rather slow on the :source command, just as Vance described. > Afterwards, the menus are a big mess. Most menu entries are not there at > all; this appears to be somehow related to those menu entries for which > keyboard shortcuts are defined, and those with submenus. For example, > Settings -> Preferences is missing completely. I'm still facing these issues with Cream 0.40 ; is there any Mac OS X binary available that works, or compilation instructions? Thanks, Wolfgang |
From: Steve H. <dig...@da...> - 2008-02-03 21:21:31
|
On Sun, 2008-02-03 at 11:43 +0100, Wolfgang Hommel wrote: > > - The MacVim version of Vim on OS X loses all of its icons and > > menus after :source'ing creamrc in. > > > > - The DarwinPorts version of Vim (compiles gvim from its sources) > > behaves rather slow on the :source command, just as Vance > > described. Afterwards, the menus are a big mess. Most menu > > entries are not there at all; this appears to be somehow related > > to those menu entries for which keyboard shortcuts are defined, > > and those with submenus. For example, Settings -> Preferences is > > missing completely. > > I'm still facing these issues with Cream 0.40 ; is there any Mac OS > X binary available that works, or compilation instructions? Sorry, I know nothing of the status of gvim on Mac (and collateral issues with Cream) other than what Vance has said here. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |