Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

History entries ending with parentheses corrupt command line on OS X 10.6.4 #150

Closed
elpres opened this Issue Sep 20, 2010 · 4 comments

Comments

Projects
None yet
2 participants

elpres commented Sep 20, 2010

When browsing the history with up/down arrows, once you get to an entry that ends with parens (i.e., any function call), the cursor jumps about 20 characters to the right and stays there until you execute the command line. Pressing arrow keys still works, but those history items appear at the same offset. Please take a look a the screenshot to see it in action; note where the cursor is. What i did was execute the first two commands and press the up arrow twice:

http://imgur.com/kDX9c.png

Installing readline fixes this behaviour.

System details: MacOS X 10.6.4, iPython 0.10 installed via MacPorts, no manual tweaks, all packages up to date.

Owner

fperez commented Sep 21, 2010

Very strange, I definitely don't see the problem on linux, and I currently have no OSX machine to test on. I'll ask on the -dev list to see if someone has seen this or has any idea (I've never had it reported, and we do have several OSX users in the dev team).

Owner

fperez commented Sep 21, 2010

Since readline fixes it, this is likely an issue with libedit (the default on the mac). We're discussing on the list whether using libedit is really viable or if readline should be a hard dependency for IPython.

Owner

fperez commented Sep 22, 2010

Add note about libedit on OS X. Closed by 45e554a.

Owner

fperez commented Sep 22, 2010

I added a more explicit note in the docs about readline being needed, we can't really support libedit's limitations.

jtriley pushed a commit to jtriley/ipython that referenced this issue Jul 30, 2011

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014

This issue was closed.

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