Issues with Eval after 8a7e371

Question

Issues with Eval after 8a7e371

markwoodhall opened this issue 9 years ago · 14 comments

Hi, thanks for all the work you are doing, still using and loving this plugin.

I do have a bit of an issue at the moment though, I've tried to understand what is causing it but I'm not sure.

All that I know for certain is that after this change 8a7e371 eval'ing anything no longer works for me. It hits the timeout and I get the .... response. Before that change everything was working fine.

I'm running neovim on Arch with the neovim python plugin and python version 3.6.0.

Thanks in advance for any help.

Cheers.
Mark

tablitza commented 8 years ago

Python 3.

Answer 1 · 2017-05-17T00:58:22.000Z

Same problem here

Answer 2 · 2017-05-17T13:15:55.000Z

Were talking about using the FsiEval command? I just tried it on mine and it seems to work ok. Can you get fsharpi working ok outside of vim?

Answer 3 · 2017-05-17T13:43:35.000Z

Yeah, fsharpi works.

Answer 4 · 2017-05-17T13:44:36.000Z

@adityavkk are you also using neovim? if so could you try with vim?

Answer 5 · 2017-05-23T17:55:21.000Z

I'm running into the same issue here as well.

Answer 6 · 2017-05-23T18:07:55.000Z

All using neovim?

…

On Tue, 23 May 2017 at 18:55, marcin-wojtowicz ***@***.***> wrote: I'm running into the same issue here as well. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIDlIyPH5wBNRoXzJNr7MCpksWFpi_Yks5r8x2KgaJpZM4NCuCL> .

Answer 7 · 2017-05-24T06:17:18.000Z

No, I'm using plain vim.

Answer 8 · 2017-05-24T06:51:26.000Z

Python3 or 2?

…

On Wed, 24 May 2017 at 07:17, marcin-wojtowicz ***@***.***> wrote: No, I'm using plain vim. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIDlEd6TOYMCLufFCfcac4j_Rm7Elshks5r88tvgaJpZM4NCuCL> .

Answer 9 · 2017-05-29T18:32:13.000Z

Same here: neovim with python3. Can #78 be merged if it solves this issue.

Answer 10 · 2017-05-29T19:22:25.000Z

I've merged #78 - please can someone test if it improves matters?

Answer 11 · 2017-05-29T19:36:04.000Z

It looks like it's working now. Thank you.

Answer 12 · 2017-05-29T19:39:26.000Z

Thanks to @xuanduc987 for the fix!

Answer 13 · 2017-05-29T19:54:04.000Z

Working for me now too. Thanks a lot @xuanduc987.