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 <[EMAIL PROTECTED]> 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 > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ cream-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cream-general
