Proposed changes to empty command handling in JDB
Chris Plummer
chris.plummer at oracle.com
Mon Aug 23 17:36:56 UTC 2021
My thoughts were actually that integrating jline would result in too
much disruption to the source, and also require a fair amount of
documentation update, but I don't know enough about what would be
involved with integrating jline to say for sure. It seems that just
adding empty command support to the few commands where it would be
useful would be much simpler, but you do also need to add a flag to
enable it (I think you would need this for jline integration also).
Chris
On 8/21/21 2:46 PM, Jakob Cornell wrote:
> Well I let this thread go quiet for a few weeks, but I did want to
> follow up on the new input we got in August. It sounds like multiple
> people are concerned about the cost of reviewing a change to JDB that
> implements GDB's empty command handling, but a patch that adds Jline
> line editing and history would be worth considering.
>
> I think I'll start looking into that change, and if I'm able to
> prepare a patch we can have some people take a look. If it's too much
> to merge then I suppose I could keep it in a fork and benefit from the
> work myself at least. In the meantime, perhaps JBS 8271356 should be
> closed, since the community isn't interested in the change. If so,
> somebody with access will need to do that.
>
> Jakob
More information about the serviceability-dev
mailing list