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

Problem Installing on OS X #28

Open
kgust opened this issue Jan 7, 2015 · 8 comments
Open

Problem Installing on OS X #28

kgust opened this issue Jan 7, 2015 · 8 comments

Comments

@kgust
Copy link

kgust commented Jan 7, 2015

I have installed the VimChat bundle. Now starting vim gives me...

$ vim
Vim: Caught deadly signal ABRT
Vim: Finished.
[1]    72948 abort    vi
$ 

I installed xmppy-0.5.0c1-py2.7.egg with easy_install xmpppy. That made no difference.

My Vim (7.4.258) is installed via Homebrew and does include +python. What am I doing wrong?

BTW, removing the plugin does cause the problem to go away.

@fifthposition
Copy link

(Disclaimer: I’m not a maintainer, just an interested would-be user who’s also had problems with installing VimChat on OS X and has never gotten it to work.)

Is that all the error it gives you (anything else from running :messages)? I don’t see a line number. Granted, there may be none, but if there happened to be one it would probably help with debugging.

Edit: Wait. Is that 72948 a line number? Now I really want to see any more message text. 😃

@kgust
Copy link
Author

kgust commented Jan 7, 2015

I'm sorry if I was unclear. Vim never starts up, that is the shell output. Vim is completely unusable in this state.

@fifthposition
Copy link

Ah ah ah. No, I think I was just a bit slow there (clearly could use more coffee).

Weird. I just tried installing it again myself and apparently failed — I ran the install script and also tried using Vundle, but I don’t see the :VimChat command — so I can’t even see if Vim starts up when it’s installed. 😞

Edit again: The Vundle problem seems to be its own issue, which I’d missed. #26

@fifthposition
Copy link

OK — just my own oversight once again (sorry!). Apparently I’d not installed xmpppy on this machine. I just did, and now with an account listed in the config file, I get:

Vim: Caught deadly signal SEGV

Vim: Finished.
zsh: segmentation fault  vim

(I’m using zsh.) So that makes two of us.

One (notable?) difference is that I don’t get the segfault until I run the :VimChat command. Vim starts up fine with the plugin installed. And the problem starts with the server communication, I’d wager; with no account in the config file, I can run the command, although nothing happens.

@kgust
Copy link
Author

kgust commented Jan 7, 2015

I'm also using ZSH but I just verified the problem is exactly the same if you use Bash.

Odd that it's dying with a different process signal (mine: ABRT, yours: SEGV).

Originally I didn't have an account in my .vimchat/config file but there was no change when I added one.

I still think there are missing dependencies, but I don't know which ones or how to install them.

@fifthposition
Copy link

I’m wondering if there are outdated dependencies. Similarly though I don’t know which ones they would be (I’m sadly no Pythonist). @ironcamel? @throughnothing?

@ironcamel
Copy link
Owner

@throughnothing uses OSX exclusively. Sorry, I only have access to linux machines. @throughnothing, want to chime in?

@ironcamel
Copy link
Owner

@kgust @fifthposition I had some trouble recently getting vimchat to run on arch linux because of a bug in the xmpppy library: eventlet/eventlet#124 (comment)

I got around it by installing this this forked version of xmppy which has patched the bug: https://github.com/ArchipelProject/xmpppy

pip install git+https://github.com/ArchipelProject/xmpppy

Can you guys try installing that and see if it fixes your issue.

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

3 participants