...

...

On 15-01-2007 at 17:17, "Andy Harrison" wrote: Right now, instead of just installing vim, it gets broken into separate components, vim, gvim, and vim-enhanced. These different versions don't work together correctly. So, for example, when I have a modeline in a file, maybe something like '# vim: et sw=3 ts=3', and then I run gvim, this modeline is completely ignored, apparently since it is a vim modeline, not gvim.

What do you mean by 'they don't work together'? in fact, gvim and vim/enhanced both require vim to be present. You can start the different versions with vim: /bin/vim gvim: /usr/X11R6/bin/gvim vim-enhanced: /usr/bin/vim-enhanced This packages are made using a single spec file. The standard vim uses these configure parameters: ./configure $RPM_ARCH-suse-linux \ --prefix=/usr \ --mandir=%{_mandir} \ --with-features=big \ --enable-cscope \ --enable-multibyte \ --with-compiledby='http://www.suse.de/' \ --disable-gpm \ --without-x \ --disable-gui \ --disable-perlinterp \ --disable-pythoninterp \ --disable-rubyinterp \ --disable-tclinter For the enhanced version, the following ./configure parameters are used: ./configure $RPM_ARCH-suse-linux \ --bindir=/usr/bin \ --prefix=/usr \ --mandir=%{_mandir} \ --with-features=huge \ --enable-cscope \ --enable-multibyte \ --enable-sniff \ --with-compiledby='http://www.suse.de/' \ --with-vim-name=vim-enhanced \ --with-tclsh=%{_bindir}/tclsh \ --enable-gui=no \ --with-tlib=ncurses \ --enable-perlinterp \ --enable-pythoninterp \ --enable-rubyinterp \ --enable-tclinterp \ --disable-xim for gvim, the configure looks like: ./configure $RPM_ARCH-suse-linux \ --bindir=/usr/X11R6/bin \ --prefix=/usr \ --mandir=%{_mandir} \ --with-features=huge \ --enable-cscope \ --enable-multibyte \ --enable-sniff \ --with-compiledby='http://www.suse.de/' \ --with-x \ --with-python-config-dir=%{py_libdir}/config \ --with-vim-name=gvim \ --with-tclsh=%{_bindir}/tclsh \ --with-tlib=ncurses \ --enable-fontset \ --enable-gui=gtk2 \ --enable-max-features \ --enable-perlinterp \ --enable-pythoninterp \ --enable-xim How else can I help you? Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 1/15/07, Marc Wilson wrote:

On Mon, Jan 15, 2007 at 04:34:45PM +0100, Dominique Leuenberger wrote:

...

How else can I help you?

Point out to him that you *do* have to *enable* support for modelines. Vim isn't going to go looking for one, unless you tell it to. :)

Thanks for the reply. However, modeline is already enabled in my .vimrc configuration file. gvim will not properly read the modeline value until the modeline is changed to "gvim." -- Andy Harrison -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I'm sorry, but my understanding of vim is only basic. I just run vim (without any parameters) and don't use gvim, whatever..., because for GUI I use KDE Kate. If you feel the need you can open a bug at openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org