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

Unable to use due to: skipping a message on shell_channel #146

Open
gzagatti opened this issue Feb 3, 2016 · 3 comments
Open

Unable to use due to: skipping a message on shell_channel #146

gzagatti opened this issue Feb 3, 2016 · 3 comments

Comments

@gzagatti
Copy link

gzagatti commented Feb 3, 2016

Hi,

I have been unable to use the plugin as everytime I start it through :IPython I get a warning message skipping a message on shell_channel. I have no clue what that means or where to start looking for answers as I don't quite understand the warning.

When I press <f5> I get a buffer where the command is printed, like an Ipython shell. However, the file is never executed.

When I head to an instance of the console and type a command, then come back to vim I can see the command printed on the Ipython vim shell.

Any help in helping to figure out what to do would be appreciated.

@gzagatti
Copy link
Author

gzagatti commented Feb 3, 2016

Hello,

I have been able get the plugin working on my machine. For some reason the default mappings were not working. Once I changed the mappings to something else I was able to get the plugin to respond.

Regarding the warning skipping a message on shell_channel which showed up upon connecting to IPython, I found out that the problem was due to the set_pid function from vim_ipython.py. That function is called from the km_from_string function. When the pid of the kernel is requested, for some reason unknown to me, the message on the shell is skipped. This does not seem to be a major issue, but I wonder what might be causing that.

Next the IPython command seems to fail when passed without an argument if there is another more recent file on the path of the find_connection_function. I would change the default of the km_from_string to the default of the find_connection_function that is kernel-*.json which seem to work most of the time.

@varung
Copy link

varung commented Oct 23, 2017

Can you explain in more detail how you fixed this? I'm hitting the same problem on Ubuntu 16

@ambiflextrous
Copy link

Same problem here don't know how to fix it.

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