[
https://issues.apache.org/activemq/browse/SMX4KNL-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49023#action_49023
]
Jamie Goodyear commented on SMX4KNL-137:
----------------------------------------
The only references to the beep command is held within the jline console,
specifically in Jline CandidateListCompletionHandler.java [1] and
ConsoleReader.java [2].
My guess would be in ConsoleReader#readLine that the series of backspaces on
Windows may cause an non-handled signal character to be processed hence causing
the final default clause to be processed (if unsuccessful identification, then
beep).
[1]
http://jline.cvs.sourceforge.net/viewvc/jline/jline/src/main/java/jline/CandidateListCompletionHandler.java?view=markup
[2]
http://jline.cvs.sourceforge.net/viewvc/jline/jline/src/main/java/jline/ConsoleReader.java?view=markup
> GShell makes a very loud beep when hitting backspace once too often on Windows
> ------------------------------------------------------------------------------
>
> Key: SMX4KNL-137
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-137
> Project: ServiceMix Kernel
> Issue Type: Bug
> Affects Versions: 1.0.1
> Environment: Windows XP
> Reporter: David Bosschaert
> Priority: Minor
>
> When using the SMX 4 Kernel GShell console, if you hit backspace once too
> often on Windows, you get a really loud beep. I guess this is to indicate
> that there is no character to delete any more, but I guess the 'normal'
> behaviour of not doing anything would be good enough too.
> On my DELL laptop the beep is so loud (even if I have my windows sound volume
> switched off) that it nearly knocks me off my chair.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
