On opening a tex file, I get: Error detected while processing /usr/share/vim/vimfiles/ftplugin/latex-suite/mathmacros.vim: line 322: E15: Invalid expression: <plug>\equiv the file is still opened though, and all features I use actually work. The Tex-Math is loaded up and is usable. I haven't opened up mathmacros.vim and figured out which function/macro/whatever the error occurs in though... I'm kinda rushed for time. -- app-editors/vim-7.0_alpha20041128 -acl -cscope -debug +gpm -minimal (-mzscheme) +ncurses +nls +perl +python +ruby (-selinux) +tcltk -vim-with-x app-editors/vim-core-7.0_alpha20041128 -acl -debug -livecd +ncurses +nls (-selinux) app-vim/latexsuite-1.5 -- Portage 2.0.51-r3 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-ck2 x86_64) ================================================================= System uname: 2.6.9-ck2 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.6 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-march=athlon64 -O2 -pipe -fweb -ftracer" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /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/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe -fweb -ftracer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache cvs distlocks sandbox sign" GENTOO_MIRRORS="ftp://gentoo.inode.at/source/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/home/slarti/cvs/gentoo-x86" PORTDIR_OVERLAY="/usr/local/portage" SYNC="cvs://slarti@cvs.gentoo.org:/var/cvsroot" USE="amd64 X aalib acpi aim alsa apm berkdb bitmap-fonts cap cdr crypt cups curl droproot dvd escreen esd f77 fam fbcon flac foomaticdb fortran gdbm gif gimpprint glx gnome gnutls gpm gstreamer gtk gtk2 gtkhtml iconv icq imagemagick imap imlib jabber jikes joystick jp2 jpeg junit libwww lzw lzw-tiff maildir mailwrapper mikmod mozilla moznocompose moznoirc moznomail mozsvg mpeg msn multilib ncurses nethack nls oggvorbis opengl oscar pam pcre pdflib perl png ppds python readline ruby samba sasl sdl spell ssl svg tcltk tcpd tetex tiff truetype truetype-fonts unicode usb userlocales xml xml2 xpm xrandr xv zlib" Thanks all, Tom
worksforme... So... Could you try vim -i NONE -u NONE and see what happens?
Okay, this is strange: vim -i NONE -u NONE: no error vim: no error gvim -i NONE -u NONE: no error gvim: error Ciaran, my .vimrc is near identical to yours, for your information. I can drop you a diff if you like.
Hm, could you just attach the whole vimrc please? I'll try the "remove bits until it works" approach. Or you could do that if you prefer :)
Created attachment 44996 [details] vimrc
22:38 < p0g> ciaranm: gentoo bug #72837 is a vim problem 22:39 < ciaranm> p0g: you managed to figure it out? 22:42 < p0g> ciaranm: yeah 22:44 < p0g> ciaranm: in version7.txt is the following line: 22:44 < p0g> Skip over the expression in `=expr` when looking for comments, |, % and #. 22:44 < p0g> that happens in separate_nextcmd in ex_cmds.c 22:45 < p0g> but it always tries to skip that 22:45 < p0g> even if the command does not take a backtick expression as an argument 22:45 < p0g> the problem with vim-latex is that it defines a menu with `= in it 22:47 < ciaranm> ok, i see it 22:47 < ciaranm> hrm 22:47 < ciaranm> could just shove a backslash in vim-latex i 'spose The function in question is vim7/src/ex_docmd.c:separate_nextcmd, in particular this bit: #ifdef FEAT_EVAL /* Skip over `=expr` when wildcards are expanded. */ else if (p[0] == '`' && p[1] == '=') { p += 2; (void)skip_expr(&p); } #endif So, it's whether this is a vim issue or a vim-latex issue...
I just tested this again, and the problem does not occur with app-editors/vim-7.0_alpha20050622. Do we just remove the block in its entirety? I have not checked with previous versions if it still occurs, but I would assume people who have unmasked vim7 are staying up to date with the latest.
Block removed.