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
Buggy linewrap in Mac OSX Terminal (Mountain Lion) #3329
Comments
Do you not get any message about |
Hello. I have this message on startup:
|
@minrk Thank you for help! I just deleted via It's works in virtual environment. Good. How can I fix this problem system wide? I see that I have not easy_install tool outside virtual_env. |
You could install easy_install systemwide, or try installing readline by downloading it, untarring and running setup.py install. I'm going to close this because the libedit problems aren't a bug we can fix. You should still be able to comment, or take it to the mailing list or Stackoverflow. |
I think that installing additional package - in't good solution. Is is able to fix this problem in your project? Thanks. |
As far as I know, no. If we could easily fix it in IPython, we would have done so a long time ago. If you can find a fix, we'd love to hear about it. |
This is a bug in libedit / Python readline, not a bug in IPython, so there is nothing for us to fix other than trying to write a big message that hopefully people will not ignore. |
I don't know what do you use in iPython internally to read lines. Do you work with lines via libedit or readline? Do you have ability to integrate readline to iPython? Or, maybe you can make a fix for MacOS. I see this bug only on MacOS, and not found this bug on Ubuntu Linux. I think that "maybe" problem in \r'n symbols in end of line on MacOS. If so, than you can handle this situation to replace \r\n to \n as used on Ubuntu Linux. Thanks you for feedback. |
What you ask is like asking : |
@1st: Macs can't ship with readline for licensing reasons (namely: it's GPL), so they have libedit instead to do the same job. Python's readline module therefore tries to use libedit, but it doesn't work properly. Ubuntu doesn't have the problem because it has 'real' readline. (To be fair, I don't know if libedit is still buggy, or if Apple just uses an old version of it) I don't see us shipping readline with IPython, both for licensing reasons and technical ones. |
I understand your position. I am not familiar with readline and libedit. I think that these libs allow you to read lines and go to history back and forward. Does libedit return incorrect data to iPython, or iPython incorrect represent these data? Maybe you can handle data from libedit to work properly? |
libedit is actually the one doing the line wrapping, not IPython. The fixes belong in libedit (or the Python readline module), and there isn't really anything IPython can do about it other than warn people that libedit is horribly broken. |
To be clear, these don't work by returning values that IPython does things with: we just initialise readline (or libedit), which then directly controls your interaction with the terminal. So when you press up to look through your history, that's handled entirely in readline, without invoking any IPython code. |
I have the same problem as described here #206
I installed readline via pip, and after this installed python via pip. I made it in virtualenv.
I see that history has wrapped lines, and sometimes I have wrapped lines if I insert line of code and navigate to middle of line.
Please fix this bug on MacOS.
The text was updated successfully, but these errors were encountered: