[
https://issues.jboss.org/browse/AS7-6004?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-6004:
----------------------------------------
The problem here is that it's not always good and expected to have a whitespace added
after the single candidate.
Generally speaking, whitespace is only a specific example of a separator. There might be
other separators expected, especially talking about the operation request format with /,
=, :, etc as separators. We discussed this we Stale at the time and I think there is some
API in Aesh supporting alternative separators.
But anyway, just adding a whitespace after a single choice as a rule will introduce other
problems.
Inconsistent tab completion behaviour between commands and arguments
--------------------------------------------------------------------
Key: AS7-6004
URL:
https://issues.jboss.org/browse/AS7-6004
Project: Application Server 7
Issue Type: Bug
Components: CLI
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Priority: Minor
When tab is used for completion, the behavior changes when there is only 1 remaining
candidate.
For commands, when the completion leads to a single candidate, a whitespace is appended
and we can proceed to the arguments
For arguments using a TabCompleter, when the completion leads to a single candidate, no
whitespace is appended and we have to type it to be able to proceed to the next argument
Example:
* deployment-over<TAB>
=> will complete to deployment-overlay<WHITESPACE><CURSOR> (a whitespace
is appended to the single candidate)
* deployment-overlay a<TAB>
=> will complete to deployment-overlay add<CURSOR> (no whitespace appended even
though add is the only candidate matched)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira