[overlord-issues] [JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI

[Eric Wittmann (JIRA)]

    [ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964530#comment-12964530 ] 

Eric Wittmann commented on SRAMP-408:
-------------------------------------

Tab completion without the s-ramp: namespace doesn't work properly when completing partial command names.  This is primarily evident with commands starting with "u".  If you type a "u" and hit Tab you do not receive the list of commands starting with 'u'.  However, if you type just a 'p' (for example) and then hit Tab you *will* get the only matching command (property).
                
> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
>                 Key: SRAMP-408
>                 URL: https://issues.jboss.org/browse/SRAMP-408
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion.  For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect".  After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end.    If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion.  I tested on Windows cygwin.  I will now go test on Fedora.

--
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