emacs freezes when ipython-complete is called #1010

Closed
paykroyd opened this Issue Nov 18, 2011 · 8 comments

Comments

Projects
None yet
3 participants
@paykroyd
Contributor

paykroyd commented Nov 18, 2011

I have the latest ipython.el, ipython 11, and python-mode 6.0.3. I've tested in aquamacs 2.4 (emacs 23.2) and in eamcs 24.0.90.1. I can reproduce this every time. I start an ipython shell, start a completion and it will freeze each time. This for example:

l = []
l.app  # then I hit tab

I don't see anything in the Messages buffer and the CPU isn't doing anything. Please let me know what I can do to help debug.

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Nov 18, 2011

Member

We know ipython.el is out of date - unfortunately, none of the core developers know emacs lisp. One or two people have done bits of work on IPython/Emacs integration (search the issues list to see), but I don't think there's anything finished we can point you to. If you do know emacs lisp, you're welcome to work on it.

Member

takluyver commented Nov 18, 2011

We know ipython.el is out of date - unfortunately, none of the core developers know emacs lisp. One or two people have done bits of work on IPython/Emacs integration (search the issues list to see), but I don't think there's anything finished we can point you to. If you do know emacs lisp, you're welcome to work on it.

@paykroyd

This comment has been minimized.

Show comment
Hide comment
@paykroyd

paykroyd Nov 18, 2011

Contributor

Sure. I'm not great with elisp debugging but I'll give it a shot. If I have questions specific to ipython, should I just post them into this issue?

On Nov 18, 2011, at 9:57 AM, Thomas wrote:

We know ipython.el is out of date - unfortunately, none of the core developers know emacs lisp. One or two people have done bits of work on IPython/Emacs integration (search the issues list to see), but I don't think there's anything finished we can point you to. If you do know emacs lisp, you're welcome to work on it.


Reply to this email directly or view it on GitHub:
#1010 (comment)

Contributor

paykroyd commented Nov 18, 2011

Sure. I'm not great with elisp debugging but I'll give it a shot. If I have questions specific to ipython, should I just post them into this issue?

On Nov 18, 2011, at 9:57 AM, Thomas wrote:

We know ipython.el is out of date - unfortunately, none of the core developers know emacs lisp. One or two people have done bits of work on IPython/Emacs integration (search the issues list to see), but I don't think there's anything finished we can point you to. If you do know emacs lisp, you're welcome to work on it.


Reply to this email directly or view it on GitHub:
#1010 (comment)

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Nov 18, 2011

Member

It's probably best to post questions to the ipython-dev mailing list, so more people see it. We only get emails from these comments once we've joined the conversation.

Member

takluyver commented Nov 18, 2011

It's probably best to post questions to the ipython-dev mailing list, so more people see it. We only get emails from these comments once we've joined the conversation.

@fperez

This comment has been minimized.

Show comment
Hide comment
@fperez

fperez Nov 18, 2011

Member

@paykroyd; just to second what Thomas said, we'd love to have some help with the emacs support. It's been languishing for a long time in a semi-broken state, which is a shame. For example, it used to correctly follow the debug source file hints, so that if you did %debug inside emacs it would nicely track your files in another buffer as you moved in the stack. At some point that functionality broke too. It's probably a small fix, but none of us has the expertise to do it and we're too swamped with the core code to have the bandwidth for this. So it would be fantastic if you could pitch in on this front.

Member

fperez commented Nov 18, 2011

@paykroyd; just to second what Thomas said, we'd love to have some help with the emacs support. It's been languishing for a long time in a semi-broken state, which is a shame. For example, it used to correctly follow the debug source file hints, so that if you did %debug inside emacs it would nicely track your files in another buffer as you moved in the stack. At some point that functionality broke too. It's probably a small fix, but none of us has the expertise to do it and we're too swamped with the core code to have the bandwidth for this. So it would be fantastic if you could pitch in on this front.

@paykroyd

This comment has been minimized.

Show comment
Hide comment
@paykroyd

paykroyd Nov 19, 2011

Contributor

@fperez, I'm happy to help; ipython is a great tool. I can't make any promises about writing brilliant elisp, but I'll start looking around and see what I can do.

Contributor

paykroyd commented Nov 19, 2011

@fperez, I'm happy to help; ipython is a great tool. I can't make any promises about writing brilliant elisp, but I'll start looking around and see what I can do.

@paykroyd

This comment has been minimized.

Show comment
Hide comment
@paykroyd

paykroyd Nov 19, 2011

Contributor

I submitted a pull request that solves this problem for me. I wasn't sure how to link them. This is linked in the pull request comments.

Contributor

paykroyd commented Nov 19, 2011

I submitted a pull request that solves this problem for me. I wasn't sure how to link them. This is linked in the pull request comments.

@fperez

This comment has been minimized.

Show comment
Hide comment
@fperez

fperez Nov 20, 2011

Member

@paykroyd, thanks! reviewing now. You can mention one in the other by number: an explicit #1015 will auto-link to PR #1015. And if a commit in #1015 mentions explicitly this bug, it will auto-link as well. See their blog post for more details on the auto-linking and closing features.

Member

fperez commented Nov 20, 2011

@paykroyd, thanks! reviewing now. You can mention one in the other by number: an explicit #1015 will auto-link to PR #1015. And if a commit in #1015 mentions explicitly this bug, it will auto-link as well. See their blog post for more details on the auto-linking and closing features.

@fperez

This comment has been minimized.

Show comment
Hide comment
@fperez

fperez Nov 24, 2011

Member

Closed by the merge of #1015.

Member

fperez commented Nov 24, 2011

Closed by the merge of #1015.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment