You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user provides a valid incomplete command, is it possible for cligen to put the user into the scope/level of the syntax structure of that command rather than returning the "Unkown command" error message ?
For example, given the following syntax....
aa {
bb;
cc;
dd {
ee;
}
}
The user types the command : "aa\n" . Cligen would then not return "Unknown Command", but allows the user to perform the commands defined inside the "aa" block at the next prompt. The prompt could contain the current scope/level of the command.
cli>aa
cli(aa)>dd
cli(aa/dd)>ee
Thanks,
Marek Gimza
The text was updated successfully, but these errors were encountered:
The building-blocks for this behavior exists, but is only partly made in cligen-only context. See "tree workpoints" in Section 2.7.2 in the cligen-tutorial.
When a user provides a valid incomplete command, is it possible for cligen to put the user into the scope/level of the syntax structure of that command rather than returning the "Unkown command" error message ?
For example, given the following syntax....
aa {
bb;
cc;
dd {
ee;
}
}
The user types the command : "aa\n" . Cligen would then not return "Unknown Command", but allows the user to perform the commands defined inside the "aa" block at the next prompt. The prompt could contain the current scope/level of the command.
cli>aa
cli(aa)>dd
cli(aa/dd)>ee
Thanks,
Marek Gimza
The text was updated successfully, but these errors were encountered: