[jboss-jira] [JBoss JIRA] (WFCORE-1019) History browsing in CLI (using the up arrow) works strangely
Ståle Pedersen (JIRA)
issues at jboss.org
Thu Nov 12 16:15:01 EST 2015
[ https://issues.jboss.org/browse/WFCORE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128542#comment-13128542 ]
Ståle Pedersen commented on WFCORE-1019:
----------------------------------------
this is an æsh bug, ill fix it in a 0.66.* version
> History browsing in CLI (using the up arrow) works strangely
> ------------------------------------------------------------
>
> Key: WFCORE-1019
> URL: https://issues.jboss.org/browse/WFCORE-1019
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 2.0.0.CR1, 2.0.0.CR5
> Reporter: Ladislav Thon
> Assignee: Alexey Loubyansky
>
> I tend to rely on history browsing in the CLI a lot, but it got broken in WildFly 10.0.0.CR1 / WildFly Core 2.0.0.CR1 (I'd guess that the cause is the AESH upgrade). Let's see:
> {code}
> rm ~/.jboss-cli-history # let's start with clean slate
> ./wildfly-10.0.0.Beta2/bin/standalone.sh
> # the following is in second console
> ./wildfly-10.0.0.Beta2/bin/jboss-cli.sh -c
> :read-resource
> :whoami
> [up arrow shows :whoami, so press Enter to run it]
> [and repeat, up arrow shows :whoami]
> {code}
> OK, that's expected. Repeat the process with WildFly 10.0.0.CR1 or CR2 and you'll find out that the second \[up arrow\] shows {{:read-resource}}. This is IMHO highly wrong and it confused me _a lot_ when I first encoutered this bad behavior.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list