Syntastic: Problem with :E

[noprompt]

After installing the plugin I get this funky error when using :E:

E464: Ambiguous use of user-defined command

Incidentally, :Ex, :Exp, :Expl, and so forth all seem to work dandily.

[noprompt]

I haven't been able to figure out the issue so far. Perhaps it's a conflict with another plugin or something weird. However, I did manage to come up with a ghetto work around in case anyone else has this issue!

cmap E<CR> Ex<CR>

This sort of thing causes blood to spray out of my eyes. Hopefully I can do some _real_ investigation when I get some free time instead of trying to put duct tape on everything I see.

[scrooloose]

the problem is that syntastic defines the :Errors command - so now just typing :E isnt enough for vim to determine what command you want to invoke. Try using :Ex instead

[noprompt]

Yeah, I noticed that earlier today. I'm just so used to using :E and habits in Vim can be tough to break. No sweat though. This plugin is awesome! Thanks!

[paulgb]

For a slightly less hacky workaround I added this to my ~/.vimrc

command E Ex

[bart9h]

I think it should be SyntasticErrors, and if the user wants to shorten it, then she can just call command Errors SyntasticErrors. Or make it configurable. I'll use paulgb solution, but I think it is good practice to avoid conflicts with broadly used commands and keys.