Open rofl0r opened 8 years ago
Wow, glad to see someone trying to use editline as a drop-in replacement for GNU readline! :-)
The editline library was never intended as a GNU readline() replacement. And although I've considered myself implementing the necessary bits and bobs for GDB to work, I never found the time during my ten years maintaining this project.
However, I would greatly appreciate any and all patches to help reach that target for editline, since we all would greatly benefit from a truly FREE readline() replacement!
yeah, having a slim drop-in replacement for the utterly bloated readline would be very nice, since it's unlikely that the GNU guys will ever switch to something else, and libedit is also rather bloated.
Yep, that'd be nice. Plain termios support for all, I say :-)
Update: edited original report slightly so it can be used as a TODO list. Some functions have now been implemented, checked.
Update: two new functions/callbacks added.
Any updates on this?
Not much no.
Just to be clear, the point of editline is not to be a replacement for alll functions in readline. If we can replace just enough to be a suitable alternative, fine, but if the size skyrockets and requirements on external libraries (not libc, but ncurses) sneak in, well then we're off the mark completely. So for me, this issue serves only as a reminder; to check against when refactoring/adding features to see if the APIs listed here can be wrangled in there without much extra effort.
I see.
Thanks for the update!
gdb 7.6 seems to be the most elaborate readline user in sabotage linux, but it can be tricked, to link against libedit instead of readline, and i hoped as well against editline...
Here's a list of missing functions: