accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Berman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4543) backslashes in shell commands are consumed when using up key
Date Thu, 29 Dec 2016 20:10:58 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786024#comment-15786024
] 

Michael Berman commented on ACCUMULO-4543:
------------------------------------------

FWIW, we have a different shell whose core engine is very similar to the accumulo shell's
(and thus also uses jline in a very similar way), which does not have this issue. It's possible
our jline versions have diverged over the years, or we're using the history API in some subtlely
different way, but I believe it should be possible to address from the shell-side.

> backslashes in shell commands are consumed when using up key
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-4543
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4543
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.7.1
>            Reporter: Michael Berman
>
> If you pull a command out of your shell history with the up key, one slash gets consumed
from each sequence of slashes. As in:
> {code}
> $ grep \\x00something\\x00
> > results...
> $ [up]
> $ grep \x00something\x00
> > no results because now you're not escaped
> $ [up]
> $ grep x00somethingx00
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message