Colons echoed multiple times by NVDA #17097

Closed
opened 2026-01-31 05:32:09 +00:00 by claunia · 5 comments
Owner

Originally created by @krzysz00 on GitHub (Mar 27, 2022).

Windows Terminal version

1.13.10734.0

Windows build number

10.0.22000.0

Other Software

NVDA 2021.3.1 (eSpeak synthesizer, if relevant). In the settings, under Keyboard, "Speak typed characters" is on and "Speak typed words" is off. Under "Speech", "Punctuation/symbol level" is "most"

Steps to reproduce

At a command prompt (I've tested this with Command Prompt, PowerShell, and Ubuntu), type a colon :

Expected Behavior

NVDA should announce "colon"

Actual Behavior

NVDA announces "colon" then, after a short delay, announces "colon" again, despite only one colon being input.

Originally created by @krzysz00 on GitHub (Mar 27, 2022). ### Windows Terminal version 1.13.10734.0 ### Windows build number 10.0.22000.0 ### Other Software NVDA 2021.3.1 (eSpeak synthesizer, if relevant). In the settings, under Keyboard, "Speak typed characters" is on and "Speak typed words" is off. Under "Speech", "Punctuation/symbol level" is "most" ### Steps to reproduce At a command prompt (I've tested this with Command Prompt, PowerShell, and Ubuntu), type a colon `:` ### Expected Behavior NVDA should announce "colon" ### Actual Behavior NVDA announces "colon" then, after a short delay, announces "colon" again, despite only one colon being input.
Author
Owner

@zadjii-msft commented on GitHub (Mar 28, 2022):

@carlos-zamora and @codeofdusk as FYIs

@zadjii-msft commented on GitHub (Mar 28, 2022): @carlos-zamora and @codeofdusk as FYIs
Author
Owner

@krzysz00 commented on GitHub (Mar 28, 2022):

Please find attached an NVDA debug log (where I hopefully didn't leave out any important log components)
nvda-colon-debug.log.txt that was the result of the following testing procedure:

  1. Have PowerShell open in the preview build
  2. Restart NVDA with debug logs enabled
  3. After the window title has been re-announced, type e
  4. Hit backspace to remove e
  5. Type : (bug occurs here)
  6. Type t
  7. Hit backspace twice (getting the announcements "t", then "colon", as expected)
  8. Type x
  9. Bring up the NVDA close dialog to create a good point to cut the log

The items that jumped out at me where the following lines (obtained via a `grep 'Speaking [')

Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 'e', EndUtteranceCommand()]
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 'e', EndUtteranceCommand()]
Speaking [LangChangeCommand ('en_US'), 'colon', EndUtteranceCommand()]
Speaking [LangChangeCommand ('en_US'), ':\n']
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 't', EndUtteranceCommand()]
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 't', EndUtteranceCommand()]
Speaking [LangChangeCommand ('en_US'), 'colon', EndUtteranceCommand()]
Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 'x', EndUtteranceCommand()]

Note that the typed colon is announced both as "colon" and as ":\n".

@krzysz00 commented on GitHub (Mar 28, 2022): Please find attached an NVDA debug log (where I hopefully didn't leave out any important log components) [nvda-colon-debug.log.txt](https://github.com/microsoft/terminal/files/8364469/nvda-colon-debug.log.txt) that was the result of the following testing procedure: 1. Have PowerShell open in the preview build 2. Restart NVDA with debug logs enabled 3. After the window title has been re-announced, type `e` 4. Hit backspace to remove `e` 5. Type `:` (bug occurs here) 6. Type `t` 7. Hit backspace twice (getting the announcements "t", then "colon", as expected) 8. Type `x` 9. Bring up the NVDA close dialog to create a good point to cut the log The items that jumped out at me where the following lines (obtained via a `grep 'Speaking \[') ``` Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 'e', EndUtteranceCommand()] Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 'e', EndUtteranceCommand()] Speaking [LangChangeCommand ('en_US'), 'colon', EndUtteranceCommand()] Speaking [LangChangeCommand ('en_US'), ':\n'] Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 't', EndUtteranceCommand()] Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 't', EndUtteranceCommand()] Speaking [LangChangeCommand ('en_US'), 'colon', EndUtteranceCommand()] Speaking [CharacterModeCommand(True), LangChangeCommand ('en_US'), 'x', EndUtteranceCommand()] ``` Note that the typed colon is announced both as `"colon"` and as `":\n"`.
Author
Owner

@codeofdusk commented on GitHub (Mar 28, 2022):

Is this fixed in the NVDA 2022.1 beta?

@codeofdusk commented on GitHub (Mar 28, 2022): Is this fixed in the NVDA 2022.1 beta?
Author
Owner

@krzysz00 commented on GitHub (Mar 28, 2022):

@codeofdusk Looks like it. Or at least I couldn't reproduce the problem either with a portable copy of the beta or with latest master.

Got any guesses for what could be going on here?

@krzysz00 commented on GitHub (Mar 28, 2022): @codeofdusk Looks like it. Or at least I couldn't reproduce the problem either with a portable copy of the beta or with latest master. Got any guesses for what could be going on here?
Author
Owner

@krzysz00 commented on GitHub (Jul 8, 2022):

Works fine on NVDA 2022, closing

@krzysz00 commented on GitHub (Jul 8, 2022): Works fine on NVDA 2022, closing
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17097