Skip to content

Unexpected reading of console output #875

Closed

Description

@nvaccessAuto

Reported by tspivey on 2010-09-02 22:28
There are two instances I've found so far where characters are read unexpectedly in console windows:

  1. When echo characters is on and read dynamic content is off, the following at a Cygwin bash prompt will echo characters until ^c is pressed:
    while :;do seq 1 100;done
    This doesn't happen when character echo is off.
  2. When read dynamic content is on and regardless of the character echo setting, the first character typed on a line will speak if there's nothing else on that line. E.g. starting to type an ed command.

Activity

  1. nvaccessAuto commented on Nov 10, 2010

    @nvaccessAuto
    CollaboratorAuthor

    Comment 1 by jteh (in reply to comment description) on 2010-11-10 18:31
    Replying to tspivey:

    1. When echo characters is on and read dynamic content is off, the following at a Cygwin bash prompt will echo characters until ^c is pressed:

    while :;do seq 1 100;done

    I'm not sure there is really much we can do about this. They look like typed characters to our code because they're near the caret and they're single characters. It might be possible to work around this in Windows 7, where i believe we get real notification of typed characters via WM_CHAR. Mick, how is this currently being blocked for consoles?

    1. When read dynamic content is on and regardless of the character echo setting, the first character typed on a line will speak if there's nothing else on that line. E.g. starting to type an ed command.

    Fixed in 6b0fdbe.

  2. nvaccessAuto commented on May 8, 2011

    @nvaccessAuto
    CollaboratorAuthor

    Comment 2 by jteh on 2011-05-08 23:04
    Actually, neither issue is fixed.

    Another related issue is reading of spurious characters when cursoring through characters in a console editor with speak typed characters enabled.

  3. frastlin commented on Feb 27, 2016

    @frastlin

    When echo characters is on in Windows 10, the last line is spelled out in the console. So for example, when I am on my user dir it says:
    c : \ u s e r s \ b r a n d o n >
    C:\users\brandon>

    one right after another. I do not remember this happening in windows 7.
    It should just read the second line.

  4. LeonarddeR commented on Jul 7, 2017

    @LeonarddeR
    Collaborator
  5. Adriani90 commented on Aug 7, 2019

    @Adriani90
    Collaborator

    @tspivey can you still reproduce this in NVDA 2019.2 RC2? @codeofdusk does your highly appreciated work on console improvements with UIA solve this issue?

  6. codeofdusk commented on Aug 22, 2019

    @codeofdusk
    Contributor

    @tspivey can you still reproduce this in NVDA 2019.2 RC2? @codeofdusk does your highly appreciated work on console improvements with UIA solve this issue?

    Is this a duplicate of #513?

  7. Adriani90 commented on Apr 25, 2020

    @Adriani90
    Collaborator

    @codeofdusk that issue was partly a duplicate.
    @tspivey how is the behavior now in NVDA 2020.1 Beta?

  8. Adriani90 commented on Aug 12, 2021

    @Adriani90
    Collaborator

    Does anyone have an update wether this issue still occurs in last NVDA alpha?

  9. codeofdusk commented on Aug 12, 2021

    @codeofdusk
    Contributor

    This is a duplicate of #513 (fixed in 2019.3).

  10. Adriani90 commented on Aug 17, 2021

    @Adriani90
    Collaborator

    Closing as works for me. Thanks for the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions