Activity

1. Frank Fesevur (ffes)

   added

   Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.

   on Aug 8, 2019
2. ghost added

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Aug 8, 2019
3. ghost added

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Aug 8, 2019
4. Dustin L. Howett (MSFT) (DHowett-MSFT)

   added

   Area-SettingsIssues related to settings and customizability, for console or terminalIssues related to settings and customizability, for console or terminal

   Area-VTVirtual Terminal sequence supportVirtual Terminal sequence support

   Issue-TaskIt's a feature request, but it doesn't really need a major design.It's a feature request, but it doesn't really need a major design.

   Product-TerminalThe new Windows Terminal.The new Windows Terminal.

   and removed

   Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Aug 8, 2019
5. ghost removed

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Aug 8, 2019
6. Dustin L. Howett (MSFT) (DHowett-MSFT)

   added this to the Terminal v1.0 milestone on Aug 8, 2019
7. DHowett-MSFT commented on Aug 8, 2019

   

   Dustin L. Howett (MSFT) (DHowett-MSFT)

   on Aug 8, 2019

   Contributor

   More actions

   This depends on #1608.
8. trajano commented on Aug 9, 2019

   

   Archimedes Trajano (trajano)

   on Aug 9, 2019

   More actions

   In addition, I want that to be configurable on both global and on profile level

   One change though, instead of the following to be default

   "bell": "enable" 
   

   use

   "bell": "default" 
   

   that way we can use

   "bell": "path to mp3,wav,ogg" 
   

   👍React with 👍1Reacted by Frank Fesevur
9. Kayla Cinnamon (cinnamon-msft)

   modified the milestones: Terminal v1.0, Terminal v1.x on Jan 23, 2020
10. 9 remaining items

    Load more
11. Mike Griese (zadjii-msft)

    modified the milestones: Terminal v1.x, Terminal v1.5 on Sep 29, 2020
12. zadjii-msft commented on Sep 29, 2020

    

    Mike Griese (zadjii-msft)

    on Sep 29, 2020

    Last edited by zadjii-msft

    Member

    More actions

    Frank Fesevur (@ffes) Absolutely, I'll make sure of that ☺️

    Note to self: we should do this as an enum like:

    "bellStyle": "audible"|"visible"|"none"
    

    We don't need to implement visible right now, but we should do it this way so we're future-proof

    ❤️React with ❤️1Reacted by Frank Fesevur
13. Dustin L. Howett (DHowett)

    added a commit that references this issue on Oct 1, 2020

    Add support for the BEL control in Windows Terminal (#7679)

    ...

    09cc5f4
14. Mike Griese (zadjii-msft)

    self-assigned this

    on Oct 1, 2020
15. ghost added

    In-PRThis issue has a related PRThis issue has a related PR

    on Oct 1, 2020
16. Dustin L. Howett (DHowett)

    closed this as completedin #7793on Oct 15, 2020
17. ghost added

    Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

    on Oct 15, 2020
18. ghost removed

    In-PRThis issue has a related PRThis issue has a related PR

    on Oct 15, 2020
19. ghost added

    Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.

    on Oct 15, 2020
20. Dustin L. Howett (DHowett)

    added a commit that references this issue on Oct 15, 2020

    Add a setting to configure the audible bell (#7793)

    ...

    This issue will close once commit 98806e2 is merged into the 'main' branch.

    98806e2
22. nathanblair commented on Nov 12, 2020

    

    Nathan Blair (nathanblair)

    on Nov 12, 2020

    More actions

    I'm on the Windows Terminal Preview from the Microsoft Store, and while I can't determine if the bell is truly disabled for a Powershell shell, I am definitely hearing it while in Alpine WSL.

    Here's what I have in my settings.json (which I allowed Terminal to recreate after installing the newest 1.5 release):

        ...
        "bellStyle": "none",
        ...
    

    I'll note that VS Code was unable to see any "bell" properties (I assume these properties are populated from the json schema).

    I have other features from 1.5 like a maximizedFocus so I'm positive I have the most recent version. Should I do a full uninstall and then install Terminal Preview fresh?
23. zadjii-msft commented on Nov 12, 2020

    

    Mike Griese (zadjii-msft)

    on Nov 12, 2020

    Member

    More actions

    Where did you put bellStyle? In the global settings (at the root of the json), or in a profile? Since bellStyle is a per-profile setting, if you want it to apply to all profiles, you'll need to put it in the profiles.defaults object:

    

    👍React with 👍4Reacted by Roman V, Christoph Krüger, Bent Alexander Haase and 0x7d7b

    ❤️React with ❤️3Reacted by Joshua Sleeper, Lana Yount and Bent Alexander Haase
24. nathanblair commented on Nov 12, 2020

    

    Nathan Blair (nathanblair)

    on Nov 12, 2020

    More actions

    Excellent call! Indeed, that fixes it. Thanks!