If you have "set compatible" in your .vimrc you get lots of errors from the gentoo-syntax plugins. For example: robwilco root # cat .vimrc set compatible robwilco root # vim --- Auto-Commands --- filetypedetect BufNewFile *.e{build,class} set filetype=ebuild gentoo BufNewFile *.e{build,class} let is_bash=1|setfiletype sh set ts=4 sw=4 noexpandtab Error detected while processing /usr/share/vim/vimfiles/plugin/newebuild.vim: line 115: E10: \ should be followed by /, ? or & --- Auto-Commands --- Error detected while processing /usr/share/vim/vimfiles/plugin/newinitconfd.vim: line 43: E10: \ should be followed by /, ? or & --- Auto-Commands --- line 46: E10: \ should be followed by /, ? or & --- Auto-Commands --- filetypedetect BufNewFile metadata.xml set filetype=gentoo-metadata Error detected while processing /usr/share/vim/vimfiles/plugin/newmetadata.vim: line 67: E10: \ should be followed by /, ? or & Hit ENTER or type command to continue Removing the "set compatible" from .vimrc makes the errors go away. Here are the versions I'm using: vim-core-6.3-r4 vim-6.3-r4 gentoo-syntax-20050211-r1 Reproducible: Always Steps to Reproduce: 1. emerge vim (which now installs gentoo-syntax via PDEPEND) 2. put "set compatible" in your .vimrc 3. run "vim" Actual Results: got the errors noted. Expected Results: no errors.... or, if gentoo-syntax will not work with 'compatible' mode, then it shouldn't be in PDEPEND, IMHO. Portage 2.0.51.19 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r6 i686) ================================================================= System uname: 2.6.10-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 11 2005, 08:34:51)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/X11/WindowMaker /etc/X11/rstart /etc/X11/serverconfig /etc/X11/starthere /etc/X11/sysconfig /etc/X11/twm /etc/a2ps /etc/apm /etc/gconf /etc/gnome-vfs-2.0 /etc/gtk-2.0 /etc/hotplug /etc/hotplug.d /etc/init.d /etc/lam-mpi /etc/nmh /etc/snort /etc/sound /etc/ssl/misc /etc/terminfo /usr/X11R6/lib/X11/xkb /usr/kde/3.3/share/config /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://spout.ussg.indiana.edu/pub/array2/linux/gentoo/ ftp://mirrors.tds.net/gentoo http://www.gtlib.cc.gatech.edu/pub/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://gentoo-install.cs.indiana.edu/gentoo-portage" USE="x86 X alsa apache2 apm arts avi berkdb bitmap-fonts cdr crypt cups curl emboss encode esd f77 fam flac font-server foomaticdb fortran gdbm gif gimpprint gnome gphoto2 gpm gstreamer gtk gtk2 imagemagick imap imlib ipv6 java jpeg junit kde ldap libg++ libwww mad mbox mikmod motif mozilla mp3 mpeg mysql ncurses nls nntp oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby samba sdl slang snmp spell ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts wmf xml xml2 xmms xprint xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Yick. Do you really want vi compatible mode set? I 'spose we could just disable gentoo-syntax when compatible until the safe script environment thing gets implemented...
It isn't really a matter of what _I_ want... ;-) We have a number of users who just want 'vi' to behave like the vi they have been using for the past 20 years so they use 'compatible' mode. They don't have any need for anything in gentoo-syntax but it is now being installed by default so they are getting it whether they want it or not. I have been unmerging gentoo-syntax but any future update will pick it up again so it's a bit of a hassle. I really don't think the use of 'compatible' mode is that rare so think it should be made to work with gentoo-syntax since that is getting installed by default. I'm a little curious why gentoo-syntax is now in the PDEPEND for vim-core. If someone wants it, why not let them emerge it? Unless I'm missing something, the basic function of vim doesn't depend on is so it just seems odd to include it as a dependency. Thanks for your help! --Rob
Ok, if we actually have someone using compatible mode then I'll add in a check. It's in PDEPEND to make various things actually work out of the box. We had a fair bit of discussion about this before adding it.
That would be ideal. Thanks much.
SVN r158:159
In 20050318, thanks.
FYI, 20050318 is working for me. Thanks!
