Arch Linux

Try gvim 7.1.156-1 from Testing.

Same error occurs with gvim 7.1.156-1.

It's not a vim error, you probably have the highlighting plugin installed (please verify and report here!) and that is broken at the moment (upstream)
Or you have some custom setting in vimrc. Out of the box, vim + gvim work no problems.
Google the E10 error, there are some options

I'm not sure what highlighting plugin you mean. All I did to install it was "pacman -S gvim". The only setting that I changed was adding "colorscheme darkblue" to the end of /etc/gvimrc.

do a pacman -Q | grep vim and post it here, I can't reproduce that at all.

$ pacman -Q | grep vim
gvim 7.1.156-1

okay, I can't reproduce that, there is likely a weird setting involved, did you google the error?

Yes, but I couldn't find any solutions. It seems like a generic error message.

well maybe it is a certain php file that screws up, can you attach one offending file?

<?php

echo "hello";

?>

Hm, I have no clue where that comes from or how to reproduce. You ar probably better off asking for that at the forums.

Bug also occurs on my laptop also running arch with latest gvim. Output of pacman -Q | grep vim is same on laptop. You sure you can't reproduce this?

Unfortunately, I also can't confirm this problem:

-----------------8<-----------------8<-----------
$ cat > test.php
<?php

echo "hello";

?>
$ gvim test.php
$ # Note there are no errors! Opened fine...
$ pacman -Q | grep vim
gvim 7.1.156-1
vim 7.1.156-1
vim-colorsamplerpack 5.0-1
$ sudo bash
# echo "colorscheme darkblue" >> /etc/gvimrc
# gvim test.php
# # Again no errors.
#
-----------------8<-----------------8<-----------

Is there anything in ~/.vim/ or ~/.gvimrc? Attached the 'standard' gvimrc - don't know if that'll help you or not.

Your attached gvimrc is the same as my gvimrc except that I put "colorscheme blue" in ~/.gvimrc and not in /etc/gvimrc. Also the output of pacman -Q | grep vim is ONLY gvim 7.1.156-1, not also vim 7.1.156-1.

I removed vim from my system, and I still can't reproduce the error. What's your output of the 'locale' command?

I think the problem is that the 'nocompatible' option is never set. Take a look at /etc/vimrc and /etc/gvimrc; only the vimrc has 'set nocompatible'. But lithium does not have vim installed, so he doesn't have /etc/vimrc. Cerebral, I'm guessing you have a .vimrc that sets nocompatible.

Steps to reproduce:
gvim test.php
:set compatible
:e
# should get errors

Also see :help E10 which explains why this happens.

You can try emailing the php.vim maintainer to see if he'll fix it for those who do use compatible.

I'm a bit confused about the vim and gvim packages. Nathan, you say that I do not have vim installed but it clearly is, just not the vim package. That is, vim comes in the gvim package. So my question is why would one install both the gvim and vim packages when gvim includes vim and gvim?

The gvim package does not provide the console vim executable.

$ pacman -R vim gvim
$ pacman -S gvim
$ vim
zsh: command not found: vim

Sure it does, it's just called "vi" not "vim" (and yes, it is actually vim).

Doing ":set nocompatible" before opening file does fix the issue.

The vi package provides the vi program which is slightly different from the vim program. vi looks for virc files, and vim looks for vimrc. Also, vim is compiled with more options, like cscope, python/ruby/perl interpretors, and X registers.

Take a look at the PKGBUILD's for all the differences:
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/vi/PKGBUILD?rev=1.16&cvsroot=Core&only_with_tag=CURRENT&content-type=text/vnd.viewcvs-markup
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/editors/vim/PKGBUILD?rev=1.14&cvsroot=Extra&only_with_tag=CURRENT&content-type=text/vnd.viewcvs-markup

okay, to explain what we have here:
1. we ship a vi as vi comaptible version to have a sufficient version of the editor in base,; however vi serves as container to ship the complete vim runtime which is also used by vim and gvim. Vi doe snot com with vim* binaries to avoid conflicts and confusuion
2. we ship a vim, that has everything to make console and X-based terminal users happy, how ever the vim binary is VERY close to the gvim binary
3. the gvim binary is essentially the vim binary linked against GTK2 everything else is the same.

What can not be done:
1. Tinker around with php.vim and others. We would have to alter to many files in the binary. and it just creates conflicts.

What can be done:
1. set nocompatible in /etc/gvimrc (easiest fix, a bit dirty though)
2. drastic change: drop vim package; provide vim as binary in gvim package and gvim as symlink, the way vim is supposed to work.
3. provide a vim package WITH a gvim compatible binray, and a dummy gvim package that provides only a gvim symlink to vim and a /etc/gvimrc, and a bunch of gvim* related symlinks to manpages
4. cleanest way IMHO, make gvim dependent on vim again, technically not necessary but this way we make sure /etc/vimrc with the necessary stuff is present

Wow, it's a lot more complex than I thought. In either case it doesn't really make sense to have an executable called "vi" running with as non-vi-compatible and an executable called gVIM which uses the vi settings and not the vim ones.

In case it still matters:
$ locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE=C
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=