errors when saving html.erb files about syntastic

[blueyed]

This looks like a permission problem. Try creating a file in that location manually.

Then, look at the function to see what it does there.

Maybe some %TEMP% environment var is set wrong.

[tmilker]

I get this same error under vim 7.3.81 on FreeBSD but it is /tmp/random_string/1 then 2, 3, etc. Permissions are correct and the directory exists while vim is running. If you touch the next file in the numeric sequence and then save, it mysteriously vanishes after you get the error.

[marcinbiegun]

It's somehow connected with executing system commands by VIM plugins, same problem occurs also in my ruby plugin. I'll let you know if I figure it out.

[johnhamelink]

I have this issue on my Macbook Pro running OSX Lion. I believe permissions are OK. I've experienced this with other similar plugins.

[scrooloose]

Hey guys, what happens if you do the check manually from the command line?

Try this command (where index.html.erb is the name of your file).

sed "s/<\%=/<\%/g" index.html.erb | ruby -e 'require "erb"; puts ERB.new(ARGF.read, nil, "-").src' | ruby -c

This is the command that the eruby syntax checker is using to get the errors in windows (*nix is pretty much the same).

[marcus]

@scrooloose When I run it from the command line I get "Syntax OK." It's only within vim that I get the error.

E40: Can't open errorfile /var/folders/25/mzz_4t296hq501n1_qwnd6kr0000gr/T/vPCtSpz/9

The directory T exists but it's empty.

Lion, MacVim 7.3.

[scrooloose]

:help E40 points to a few possible causes:

1. &shellredir is screwed - this is possible since syntastic does temporarily change it in the core. Are other syntax checkers working as expected for you guys? If so, i'd say that rules out this possibility.

2. &makeprg could not be executed. This is also possible given the makeprg for eruby is pretty insane. Open an erb file and try this out:

   :let &makeprg='sed "s/<\%=/<\%/g" '. shellescape(expand("%")) . ' \| RUBYOPT= ruby -e "require \"erb\"; puts ERB.new(ARGF.read, nil, \"-\").src" \| RUBYOPT= ruby -c'
   :lmake
   

This is roughly what syntastic is doing to get a list of errors for eruby files. If this fails with the permissions error then it looks like the makeprg in the eruby syntax checker is screwed somehow.

[rafaelfranca]

I'm with the same issue here, but with a .rb file. It always occurs when I'm using the same MacVim windows for more than 30 minutes.

[jonte]

I ran in to a similar problem when I swapped out bash for the fish shell. I fixed it by putting "set shell=/bin/bash" in my vimrc.
edit: just noticed I actually use /bin/sh, not /bin/bash

[marcus]

@jonte 's solution also worked for me. I use zsh by default.

[nyc]

Had a similar issue opening up '.rb' files and getting 'E484'. @jonte 's solution worked perfectly. I use fish shell as well.

[PokerMakyo]

Is there any fix for this issue for windows platform?

[zilongshanren]

I have the same issue at windows platform,hope someone can't post fix for windows platform too.
Thanks.

[drobati]

I just recently ran into this issue too. I'm running Windows 7.

shell=C:\Windows\system32\cmd.exe

I wonder If I installed Cygwin and set shell to bash how successful would I be?

[benjstephenson]

I'm also experiencing the same issue under Vim 7.1 on HPUX using ksh. I think the issue is in the SyntasticMake function, where the &shell variable is temporarily changed to "/bin/bash". My system does not have bash installed, setting this variable to "/bin/ksh" seems to stop the error occurring but when an error is detected it is then drawn around the middle of the Vim window and no error list window is opened.

[lcd047]

Hmm. Try ba13a3d, it should fix the "/bin/bash" problem.

[benjstephenson]

I'm away from work for 2 weeks but I'll give that fix a go as soon as I get back and let you know how it goes

[Forethinker]

@drobati My Syntastic is working with cygwin's bash. I have the following line in my .vimrc:

if has ("gui_running")
    set shell=C:/cygwin/bin/bash
    set shellcmdflag=-c
    set shellxquote=\"
endif

I have the if conditional on, because I use non-gui vim on bash sometimes and I want to use the flags for gVim only.

[drobati]

@Forethinker I installed cygwin and modified my vimrc, but I have problems with pylint being run through cygwin when python is installed on windows.

Simply executing pylint doesn't work. You must pass the windows path to python. Cygwin used a cygwin path which python did not except.

[Forethinker]

@drobati I have not tested python on gVim, but that sounds right. You might be able to use cyg-wrapper to get the cygwin version of python to work, but out of the box, the underlining difference in slash will make it not work. There is compiled version of windows gvim 64-bit compiled with python if you need +python-interp.

[drobati]

@Forethinker I have a +python version of gvim 64-bit I just want synatstic to work like it did on Ubuntu.

[benjstephenson]

@lcd047 Gave this a go and it fixes the error from Vim. Only thing is when a syntax error is detected it is printed to the bottom of the screen and corrupts the display. I just took a look at the shell we are using and it's rather old (Version 11/16/88 !!) so I'm guessing it's possibly just too old to support the things syntastic is doing.