Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid ruby.vim syntax #663

Open
leeeeeee opened this issue Jun 29, 2016 · 5 comments
Open

Invalid ruby.vim syntax #663

leeeeeee opened this issue Jun 29, 2016 · 5 comments

Comments

@leeeeeee
Copy link

I'm using the latest Janus in Zsh 5.2 on Mac OS (El Capitan). However, whenever I open a ruby file, new or old, I get the following warnings:

screen shot 2016-06-29 at 11 14 54 am

I had to take a screenshot because the warnings flashed before the file loaded and weren't scrollable in the terminal window. Janus is usable otherwise (as far as I can tell), but the warning message is rather annoying.

@cweilemann
Copy link

+1

@kalbasit
Copy link
Member

kalbasit commented Jul 7, 2016

I just pushed 933f5d0 please run rake to update Janus, does it solve this problem?

@cweilemann
Copy link

I actually got it working late last night by installing the homebrew version of vim... I'm guessing that it's likely because the OS X version of vim is lagging behind. The homebrew version of vim no longer has this problem.

I've uninstalled the homebrew version of vim, ran rake, and tried opening vim again and got the same error.

$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Apr  5 2016 14:53:37)

But with homebrew:

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 30 2016 15:56:05)

It works.

@leeeeeee
Copy link
Author

leeeeeee commented Jul 7, 2016

For reference, I've had this issue happen even when I was using the brew vim -- and I checked, it's VIM 7.4.

But anyway, I updated Janus, and as long as I actually invoke vim directly, I avoid the warning -- but if enter vi some_file.rb, then I get the warning, so I suppose at this point it's more of a local issue. Looks good now, thanks!

EDIT: And I've confirmed it -- when I vi a file and run :ve, it shows that it's version 7.3! Whereas vim's :ve reports 7.4.

@alvincrespo
Copy link

@cweilemann Thanks for the note there. That helped me out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants