starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Unable to disable bash audible bell when connected to a remote server via ssh #13182

New Issue
Closed
opened 2026-01-31 03:36:00 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:36:00 +00:00
Owner
Copy Link

Originally created by @thistlillo on GitHub (Mar 25, 2021).

I disabled the audible bell of the bash ( version 5.0.17(1)-release) in WSL2 by adding the usual set bell-style none. When I run it "directly" (I mean: I click on its icon), I have no problems:

  • the bell does not ring when I am working locally
  • the bell does not ring when I am connected to a remote server.

However, when the same bash shell is run inside of a Windows Terminal (1.6.10571.0 on Windows 10 Pro) the behaviour changes:

  • the bell does not ring when I work locally
  • the bell DOES RING when I am connected to a remote (linux) server via ssh.

I disabled the audible bell also on the remote server, but Windows Terminal ignores the settings and just plays the bell.

I think this is a bug.

Originally created by @thistlillo on GitHub (Mar 25, 2021). I disabled the audible bell of the bash ( version 5.0.17(1)-release) in WSL2 by adding the usual `set bell-style none`. When I run it "directly" (I mean: I click on its icon), I have no problems: - the bell does not ring when I am working locally - the bell does not ring when I am connected to a remote server. However, when the same bash shell is run inside of a Windows Terminal (1.6.10571.0 on Windows 10 Pro) the behaviour changes: - the bell does not ring when I work locally - the bell DOES RING when I am connected to a remote (linux) server via ssh. I disabled the audible bell also on the remote server, but Windows Terminal ignores the settings and just plays the bell. I think this is a bug.
claunia commented 2026-01-31 03:36:02 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 25, 2021):

the bell DOES RING when I am connected to a remote (linux) server via ssh.

So this is basically the only thing you didn't expect and think is a bug, right?

I disabled the audible bell also on the remote server

How do you do this, exactly?

@skyline75489 commented on GitHub (Mar 25, 2021): > the bell DOES RING when I am connected to a remote (linux) server via ssh. So this is basically the only thing you didn't expect and think is a bug, right? > I disabled the audible bell also on the remote server How do you do this, exactly?
claunia commented 2026-01-31 03:36:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 25, 2021):

That sure is strange. If the bell isn't playing in conhost (i.e. "opened WSL directly") when connected via ssh, then there's no reason that the Terminal should be. The Terminal uses a hidden conhost to process all the output from the client application, so if the conhost isn't ever getting the BEL, then there's no reason for the Terminal to bell (because conhost won't be sending one to the Terminal).

What are you doing in the remote server to cause the bell to be emitted?

@zadjii-msft commented on GitHub (Mar 25, 2021): That sure is strange. If the bell isn't playing in conhost (i.e. "opened WSL directly") when connected via ssh, then there's no reason that the Terminal should be. The Terminal uses a hidden conhost to process all the output from the client application, so if the conhost isn't ever getting the BEL, then there's no reason for the Terminal to bell (because conhost won't be sending one to the Terminal). What are you doing in the remote server to cause the bell to be emitted?
claunia commented 2026-01-31 03:36:02 +00:00
Author
Owner
Copy Link

@thistlillo commented on GitHub (Mar 25, 2021):

Sorry, you are right.
I was expecting the terminal not to beep also when connected to a remote server (as it behaves when working on the local machine).

When I say that I disabled the audible bell also on the remote server, I mean that I added set bell-style none for the remote shell too (bash shell).

The bell is played by, for example, using tab to auto-complete filenames.

@thistlillo commented on GitHub (Mar 25, 2021): Sorry, you are right. I was expecting the terminal not to beep also when connected to a remote server (as it behaves when working on the local machine). When I say that I disabled the audible bell also on the remote server, I mean that I added `set bell-style none` for the remote shell too (bash shell). The bell is played by, for example, using `tab` to auto-complete filenames.
claunia commented 2026-01-31 03:36:03 +00:00
Author
Owner
Copy Link

@thistlillo commented on GitHub (Mar 25, 2021):

Sorry, I made some other attempts and I was wrong.
This is the behaviour:

  • shell run on its own window. The ubuntu (bash) shell behaves correctly both locally and remotely. After set bell-style none, I see no 'signs' when, for example, I ask the auto-completion of ambiguous names.

  • shell run inside of windows terminal. The set bell-style none is ignored. The shell does not play any sound, but there is the visible bell locally (window flashes). When connected to the remote server, a sound is played.

Sorry for the confusion.

The command set bell-style none is in ~/.profile. I tried 1) to add it to ~/.bashrc and 2) to both of them, but this behaviour stays the same.

@thistlillo commented on GitHub (Mar 25, 2021): Sorry, I made some other attempts and I was wrong. This is the behaviour: - shell run on its own window. The ubuntu (bash) shell behaves correctly both locally and remotely. After `set bell-style none`, I see no 'signs' when, for example, I ask the auto-completion of ambiguous names. - shell run inside of windows terminal. The `set bell-style none` is ignored. The shell does not play any sound, but there is the `visible` bell locally (window flashes). When connected to the remote server, a sound is played. Sorry for the confusion. The command `set bell-style none` is in `~/.profile`. I tried 1) to add it to `~/.bashrc` and 2) to both of them, but this behaviour stays the same.
claunia commented 2026-01-31 03:36:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 25, 2021):

The command set bell-style none is in ~/.profile. I tried 1) to add it to ~/.bashrc and 2) to both of them, but this behaviour stays the same.

Uh, that's not the right place to put that - you need to add that to /etc/inputrc.

Check https://stackoverflow.com/a/36726662 - I know it mentions WSL specifically, but that applies to pretty much any linux install.

@zadjii-msft commented on GitHub (Mar 25, 2021): > The command `set bell-style none` is in `~/.profile`. I tried 1) to add it to `~/.bashrc` and 2) to both of them, but this behaviour stays the same. Uh, that's not the right place to put that - you need to add that to `/etc/inputrc`. Check https://stackoverflow.com/a/36726662 - I know it mentions WSL specifically, but that applies to pretty much any linux install.
claunia commented 2026-01-31 03:36:03 +00:00
Author
Owner
Copy Link

@thistlillo commented on GitHub (Mar 25, 2021):

Ok, so I solved setting it in ~/.inputrc on the remote server. There is no need to modify /etc/inputrc since it contains global configuration values that can be overridden by the users.

Basically the two shells (the local and the remote) read the user configuration files in a different order: in the remote one, the .profile is read before the .inputrc (that did not exist, so the shell read /etc/inputrc).

Thank you for your help!

@thistlillo commented on GitHub (Mar 25, 2021): Ok, so I solved setting it in `~/.inputrc` on the remote server. There is no need to modify `/etc/inputrc` since it contains global configuration values that can be overridden by the users. Basically the two shells (the local and the remote) read the user configuration files in a different order: in the remote one, the .profile is read before the .inputrc (that did not exist, so the shell read /etc/inputrc). Thank you for your help!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13182
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?