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

pyferret.start() messes up command history in python #1053

Closed
karlmsmith opened this issue Nov 23, 2017 · 1 comment
Closed

pyferret.start() messes up command history in python #1053

karlmsmith opened this issue Nov 23, 2017 · 1 comment

Comments

@karlmsmith
Copy link
Contributor

karlmsmith commented Nov 23, 2017

Reported by @karlmsmith on 5 Jan 2011 19:54 UTC
After executing pyferret.start(), the up/down arrow keys to go through the command history in python no longer work. The escape strings are printed instead of being captured. The command history still works in ferret when pyferret.run() is executed.

This was not a problem when the python includes were not part of the build of original ferret code. In fact, they used to share the command history which was nice to have. Maybe two copied of the readline library are somehow getting used?

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1781

@karlmsmith
Copy link
Contributor Author

karlmsmith commented Nov 23, 2017

Comment by @karlmsmith on 11 Apr 2011 16:40 UTC
PyFerret built at home under Ubuntu does not have this problem. Ends up this is an issue in the readline 5.0 library used by RHEL 5. Upgrading to readline 6.2 solves this problem. However, using 6.2 the Python and the Ferret histories are separate. The version of readline under Ubuntu (and what I had used back on Porter) still has the shared histories.

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

No branches or pull requests

1 participant