Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1019

History browsing in CLI (using the up arrow) works strangely

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 1.0.2.Final
    • 2.0.0.CR1, 2.0.0.CR5
    • CLI
    • None

    Description

      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:

      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]

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1177 History browsing in CLI (using the up arrow) works strangely

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. AESH-339 prev history do not reset the last fetched id if it was identical to the last one

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              olubyans@redhat.com Alexey Loubyansky
              lthon@redhat.com Ladislav Thon
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: