LustyExplorer stays open, clobbers buffer, unable to quit vim w/stacktrace

[bennidhamma]

Used to work great for me. I've recently updated vim to 7.3 (inc. patches 1-831), so I could get YCM working. I think it was around that lusty stopped behaving correctly. Strangely, it appears to alternate between correct behavior and incorrect behavior.

If I hit lr, the file view is enormous - takes up the entire vim window. If I then attempt to open a file, that file "opens" (the status bar's filename is correct), but the content of the buffer is the LustExplorer directory listing I was in. I cannot edit that buffer, nor create new buffers, nor switch buffers, and if I try to close vim, I get the following stack trace:

Cannot find the correct window! assertion failure (eval):266:in assert' (eval):647:incleanup' (eval):991:in open_entry' (eval):638:inchoose' (eval):516:in key_pressed' (eval):842:inkey_pressed' (eval):266 (eval):252:in `profile' (eval):266 Press ENTER or type command to continue

I have to kill the process and restart.

But if I cancel out of the lusty view (instead of opening a file), and reopen it, everything works correctly the second time. The lusty view is the usual tiny few lines at the bottom of vim, and when I select a file, it closes correctly.

This behavior appears to alternate every time I open and close lusty explorer.

[sjbach]

I've observed this as well on a computer with this Vim configuration:

$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May  4 2012 04:22:36)
Included patches: 1-429
...
-lruby1.8

But a computer with this Vim configuration is fine:

$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Apr  2 2013 09:18:18)
Included patches: 1-547
...
-lruby-1.9.1

What version of Ruby is your Vim linking?

[bennidhamma]

hmmm 1.8! Now I can't remember why I changed it. I think that might must have happened when I upgraded my vim. I used an internal binary that some co-workers prepared. I'll see if I can link 1.9. Thanks!

[sjbach]

Did you try this, and if so, did it solve your problem? There's probably still something to fix here; if nothing else, a warning that Vim 7.3 behaves badly with Ruby 1.8.

[bennidhamma]

Haven't been able to fix it. Have to recompile vim I think, I usually use ppas so this is a new level of vim-y-ness for me. I'll let you know if/when I get it working. On Sep 3, 2013 9:58 AM, "Stephen Bach" notifications@github.com wrote:

Did you try this, and if so, did it solve your problem? There's probably still something to fix here; if nothing else, a warning that Vim 7.3 behaves badly with Ruby 1.8.

— Reply to this email directly or view it on GitHubhttps://github.com/sjbach/lusty/issues/94#issuecomment-23728535 .

[sjbach]

I'm pretty sure I've fixed this - please let me know if not. Context: 131b3d612eca9accd624cf72bccb049a5c90d800.

[bennidhamma]

Hooraay!!! Thank you SO MUCH Stephen! I was going crazy not being able to open up files in a files current directory. That feature (,lr) is soooo good.

Thank you thank you thank you :+1: :100:

[sjbach]

Happy to help. :-)