You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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
The text was updated successfully, but these errors were encountered: