Psreadline: Should not beep on backspace with cursor at start of line

Created on 16 Aug 2016  路  6Comments  路  Source: PowerShell/PSReadLine

Beep on backspace with cursor at start of line should not be the default behavior for the default EditMode (-EditMode Windows), but it currently is that way in PowerShell 5.1 (Win10 1607 14393.51).

Right now people are forced to figure out that they must do things like put Set-PSReadlineOption -BellStyle None in their PowerShell profile, or run net stop beep + sc config beep start= disabled, to stop the beeping, as it does not honor the Sounds control panel "No Sounds" scheme, and beeps anyway.

If this change was only intended for -EditMode Vi, maybe as parity, then it should only be the behavior for that edit mode, but should not be the default behavior for -EditMode Windows.

See also http://superuser.com/questions/1113429/disable-powershell-beep-on-backspace

Most helpful comment

I vote for making it an option... :+1: :smile:

I'm trying to keep the default behavior as close to bash, cygwin, etc.

All 6 comments

Beeps are annoying. @srdubya - is this really expected in vi mode?

I just fired up Bash on Ubuntu on Windows with "set -o vi" and it beeps under this circumstance. With that said, I have no objection to taking it out or making it an option which defaults to off.

I vote for making it an option... :+1: :smile:

I'm trying to keep the default behavior as close to bash, cygwin, etc.

I just noticed it beeps in emacs mode mode on bash - so it's consistent - it definitely shouldn't beep in Windows mode.

I'm not a fan of too many configuration options. If the only justification is to keep behavior as close as possible to bash, then I'll probably just remove the beep. If there is a better justification, I'll reconsider.

Any news on this? It's a (very annoying) bug that's been there for a rather long time now and no updates here...

I've been "forced" to disable the beep service in the office, as it was annoying everyone around me. I realize that I can disable it via Set-PSReadlineOption and a PS profile, but that's just another workaround, not a real fix.

I'm just busy with other things, hopefully I'll get a new release out with some important fixes soon

Was this page helpful?
0 / 5 - 0 ratings