We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Most "industry" CLI use mainly 3 shortcuts in order to trigger CLI completion.
<Tab>
<Space>
<?>
<shift>
JunOS CLI enables the 3 of them above which has the benefit of:
Completer
Menu
-> description handling decided here has to disable <space> completion
description
<space>
IOS-XR/XE enables only [1] and [3] :
sh run
show running-configuration
-> description handling decided here has to adjust with <space> usage The command entered needs to be "normalized" during Validation step.
JunOS style seems to be easier (reedline library check needed) to implement (granted that object description case can be easily handled)
The text was updated successfully, but these errors were encountered:
Completion trigger binding added for <?>. related to issue #2 please note that <space> trigger will be implemented along side in issue #1
Sorry, something went wrong.
frederic-loui
No branches or pull requests
Most "industry" CLI use mainly 3 shortcuts in order to trigger CLI completion.
<Tab>
character<Space>
character<?>
character (mostly triggered in conjunction with<shift>
)JunOS CLI enables the 3 of them above which has the benefit of:
Completer
andMenu
.->
description
handling decided here has to disable<space>
completionIOS-XR/XE enables only [1] and [3] :
Completer
andMenu
.sh run
instead ofshow running-configuration
->
description
handling decided here has to adjust with<space>
usageThe command entered needs to be "normalized" during Validation step.
JunOS style seems to be
easier(reedline library check needed) to implement (granted that objectdescription
case can be easily handled)The text was updated successfully, but these errors were encountered: