Jim just ninja’d the discussion with his point that we could add methods for
adding command completions to existing commands and I actually agree that’s the
better idea (especially since this is abstracting away the actual option
parsing from the user and it can be better integrated into the cur
Nested command completion works. I want to complete parameters of
commands based on information from the debugged process (attributes of
an object, etc.).
> 1. break the ABI for this class and somehow let people know they need to
> recompile their plugins for the next release.
I'd rather not bre
> On Oct 7, 2019, at 3:35 AM, Raphael “Teemperor” Isemann via lldb-dev
> wrote:
>
> To my knowledge there is no way to have completions for custom commands. If
> you just want completions for nested commands (e.g., having a “custom add”
> and “custom remove” commands and want completions for
To my knowledge there is no way to have completions for custom commands. If you
just want completions for nested commands (e.g., having a “custom add” and
“custom remove” commands and want completions for completing “add” and
“remove”), then this should work if you build the nested command using
Is there a way to create custom argument completion handlers for
commands introduced by LLDB plugins? I want to add completion for some
commands on llnode (https://github.com/nodejs/llnode), but I couldn't
find a way to do so using the C++ public API.
Based on this comment
(https://github.com/llvm
