[
https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin....
]
Eric Wittmann commented on SRAMP-408:
-------------------------------------
Testing the latest changes, I found that the extra-space issue with s-ramp:query has been
fixed. However tab-completion doesn't work quite right within the query. For
example:
{code}
s-ramp> query "/s-ramp/e
{code}
Hitting 'tab' at this point yields nothing. It *should* result in:
{code}
s-ramp> query "/s-ramp/ext
{code}
If I have this:
{code}
s-ramp> query "/s-ramp/s
{code}
And then I hit 'tab', it correctly prints out the three possible completions that
start with 's'. But if I then add an 'e' it doesn't auto-complete the
one singular match.
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