On 7/15/16 11:24 AM, Carlos Pita wrote:
>> Sure, but that still requires that the application that calls readline to
>> be changed. If the problem is that applications (like ipython) don't get
>> Am I misunderstanding you?
>
> I think I'm misunderstanding you. I thought rl_callback_read_char was
> some place where rl was always returning and thus a good place to hook
> the update. If not, is there any place, say a main event loop, like
> that? I don't know anything about rl internals.
OK, let me try to clarify. When I say "applications" I mean things like R,
python, and gdb that use Readline for editing. I thought that the problem
was a reluctance by the maintainers of these applications to change their
code to deal with readline changes, or mismatches in updates so that
readline gets changed before the calling applications change to match it.
If that's not a problem, in your view, then an application-settable
variable that is tested in rl_callback_read_char is probably the right
place to solve it.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/
_______________________________________________
Bug-readline mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-readline
