Bisectly on Gvim freezes

[stoicAlchemist]

I have a recurrent problem and I think it's related to a plugin. I use gVim and installed your plugin to try figure out the faulty part on my configs but I can't run Bisectly from gVim. I assume it's because it want's to run vim instead of gVim and it just waits for the new vim instance to close, but the instance never came to spawn and it's waiting on the limbo, I mean, the new process vim is there, but I can't interact with it. I could change on line 36 and add a

if has("gui_running")
let g:vim_exe = 'gvim'
else
let g:vim_exe = 'vim'
endif


But then I don't know where to make it wait until I set Zombies or Unicorns. Any ideas?

[dahu]

Hi,

Thanks for trying Bisectly.

Bisectly "works" in gvim but as you've seen, you can't see what's happening.
Remove the silent! from line 97 in plugin/bisectly.vim to see the
progress. You can interact with gvim, but it's ugly. The better solution
here is to write a script (like the two examples provided with bisectly:
f-jumpss-over-lines.vim and View_command.vim) and call it like: :Bisectly
so f-jumps-over-lines.vim

In your script, use :Zombies when the behaviour is observed - whether or
not you consider the behaviour pleasant.

Good luck.

Cheers,
Barry

On 2 July 2014 04:57, Brian I. Martínez Estrada notifications@github.com
wrote:

I have a recurrent problem and I think it's related to a plugin. I use
gVim and installed your plugin to try figure out the faulty part on my
configs but I can't run Bisectly from gVim. I assume it's because it want's
to run vim instead of gVim and it just waits for the new vim instance to
close, but the instance never came to spawn and it's waiting on the limbo,
I mean, the new process vim is there, but I can't interact with it. I could
change on line 36 and add a

if has("gui_running")
let g:vim_exe = 'gvim'
else
let g:vim_exe = 'vim'
endif

But then I don't know where to make it wait until I set Zombies or
Unicorns. Any ideas?

—
Reply to this email directly or view it on GitHub
#1.

[stoicAlchemist]

It seems the problem I'm having is random, is there a way to trigger bisectly on the fly and reproduce the Zombie ?

[dahu]

In subsequent tests yesterday, Bisectly did NOT behave in gvim. :-( In my
prior test, I'd forgotten to force the use of gvim in g:vim_exe.

Bisectly doesn't look at the current session - it spawns a set of new
sessions.

You could try a variety of other measures though. This would be easier to
debug in real-tmie. Have you tried asking on freenode's #vim for
assistance? I'm bairui there.

On 2 July 2014 23:44, Brian I. Martínez Estrada notifications@github.com
wrote:

It seems the problem I'm having is random, is there a way to trigger
bisectly on the fly and reproduce the Zombie ?

—
Reply to this email directly or view it on GitHub
#1 (comment).

[stoicAlchemist]

Hi, sorry for the delay, I got distracted, I scratched all my vim
configs and started again adding one by one, so far I got rid of a lot
of plugins that I don't use any more and the problem hasn't show, so I
think I will do more tests and if I find something, I'll let you know.

Thanks for the responses, great plugin by the way, I'll be sure to have
it close to me next tests :)

On 02/07/14 17:40, Barry Arthur wrote:

In subsequent tests yesterday, Bisectly did NOT behave in gvim. :-( In my
prior test, I'd forgotten to force the use of gvim in g:vim_exe.

Bisectly doesn't look at the current session - it spawns a set of new
sessions.

You could try a variety of other measures though. This would be easier to
debug in real-tmie. Have you tried asking on freenode's #vim for
assistance? I'm bairui there.

On 2 July 2014 23:44, Brian I. Martínez Estrada
notifications@github.com
wrote:

It seems the problem I'm having is random, is there a way to trigger
bisectly on the fly and reproduce the Zombie ?

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub
#1 (comment).