[
https://issues.apache.org/jira/browse/KARAF-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105077#comment-15105077
]
Serge Huber commented on KARAF-4072:
------------------------------------
Ok I just tested this on my Windows 10 machine and Karaf 4.0.4
If I start karaf using “karaf start” from the CMD.exe and use the shell console
the backspace key and arrow key work normally. I tested with the Windows
Powershell and it works fine also.
If I connect using Putty to the SSH Shell then the backspace key doesn’t work
and it looks like a whitespace characters is inserted. So it might be something
to do with the detection of the terminal emulation with Putty. Also the up and
down arrows keys also seem to have issues because the line doesn’t seem to be
properly erased. It seems mostly like a display issue because if I enter “aa”
and hit backspace and then enter, Karaf tries to execute a command called “a”,
so the backspace has indeed modified the string properly. The same is true for
the up and down arrows. I tested this with Putty 0.62, 0.66 (beta) and the
latest snapshot (2016-01-04.51465fa and the behavior was the same in all of
them. I use the default settings.
I also tested with AbsoluteTelnet10.12 (demo license) and I got the exact same
behavior.
I hope this information helps.
> Karaf shell not working properly in windows
> -------------------------------------------
>
> Key: KARAF-4072
> URL: https://issues.apache.org/jira/browse/KARAF-4072
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 4.0.2
> Environment: Windows x64
> Reporter: Ankur Nema
> Attachments: karaf_shell_issue.PNG, karaf_shell_issue_2.PNG
>
>
> I have recently installed karaf 4.0.2 on windows x64. After install karaf
> shell is not working properly. When ever I am trying to press tab for auto
> complete behaviour is strange. I am attaching snapshot for same.
> Also delete button is also not working properly. When I press delete then
> cursor moves one position ahead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)