This sounds like a great thing to add. I have no problems with it.
Note that we used to have a readline capability, but we removed it
due to some of the GPL/LGPL licensing conflicts.
Please let me know if you complete this in the future. I'm still
planning to roll a 4.0 release as soon as I talk to the IBM folks
about the last code drop I gave them.
For those who are working directly in the tree, you'll note we're
now moving from 'vmdump' to 'dump' conventions, and hopefully all
the future scripts will use this as well.
Also, I spoke to someone at MCL, and we'll see how we can roll in
mcore into the LKCD project in some capacity.
Have at it, Naomi-san. :)
--Matt
naomi@xxxxxxxxxxxxxxx wrote:
>
> Hello.
> Recently, I think that lcrash should have "sub-commands line completion".
>
> Lcrash has many sub-commands. And almost sub-commands have parameters such as
> filename or symbol name which should be specified.
> The present lcrash cannot complete on sub-commands line.
> For this reason, we have to memorize sub-commands names and parameters
> exactly.
> It is very inconvenient.
> So I'll add completion capability to librl.
>
> I'm considering as follows.
> While editing sub-commands line, if TAB key is pressed, lcrash completes the
> line (or do something as bash does).
> Lcrash will complete on sub-commands names with behavior almost equivalent to
> bash.
> And I consider that parameters of sub-commands have different characteristic
> each other, I'll add the mechanism let you be able to make your own completion
> function. Using this mechanism, you can call the function that behaves as you
> want when TAB key is pressed.
>
> As the first phase, I will show the completion on sub-commands names by the
> middle of the month in September.
> And as the next phase, I will show the mechanism of sub-commands parameters
> completion with some sample source using it.
>
> Is anybody considering sub-commands line completion?
> Any comments and suggestions are welcomed.
>
> Naomi Haseo
|