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

No new windows and problems with mvim as editor for commits #340

Closed
bitboxer opened this issue Jan 1, 2012 · 9 comments
Closed

No new windows and problems with mvim as editor for commits #340

bitboxer opened this issue Jan 1, 2012 · 9 comments

Comments

@bitboxer
Copy link

bitboxer commented Jan 1, 2012

I just tried to switch from the old rakefile based janus to the new one, but currently this is not working for me :( .

I am using rvm and I am using the define_vim_wrappers method. But there are two problems:

  1. I can't open a new window with File > New Window. I see this on the console:

    Vim: Caught deadly signal SEGV
    Vim: Finished.

  2. I have configured mvim for my editor with "mvim -f" but this fails also with the same SEGV .

How can I find out what exactly is the cause for this SEGV ?

@bitboxer
Copy link
Author

bitboxer commented Jan 1, 2012

Btw: the wrapper is working, as a proof the which mvim :

mvim () {
(
    unset GEM_HOME
    unset GEM_PATH
    /usr/local/bin/mvim $@
)
}

@kalbasit
Copy link
Member

kalbasit commented Jan 3, 2012

Try patching the mvim shell script

$ cd /
$ curl -Lo- http://bit.ly/mvim-remove-rvm-hacks | sudo patch -Np1

@bitboxer
Copy link
Author

bitboxer commented Jan 3, 2012

Nope, that doesn't help.

@kalbasit
Copy link
Member

kalbasit commented Jan 3, 2012

That's weird, could you please Gist your mvim file ?

@bitboxer
Copy link
Author

bitboxer commented Jan 3, 2012

@bitboxer
Copy link
Author

bitboxer commented Jan 8, 2012

I have now switched back to the old system till this is fixed :( . When there is anything I can do to help, please let me know!

@kalbasit
Copy link
Member

Watch #352 and #348 this will be resolved when both issues are closed, which I am working on as we speak.

@bitboxer
Copy link
Author

Great. Will watch those.

@bitboxer
Copy link
Author

yes, now it is working again.

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

2 participants