Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSX Accessibility - speaking selected text in the Sublime window instead speaks the window title #1420

Open
1 of 3 tasks
phkn opened this issue Sep 29, 2016 · 5 comments
Open
1 of 3 tasks

Comments

@phkn
Copy link

phkn commented Sep 29, 2016

Summary

OSX Accessibility - speaking selected text in the Sublime window instead speaks the window title

Expected behavior

The selected text in the window should be sent to the speech synthesis server / TTS engine

Actual behavior

The actual text in the editor window is ignored, and the title of the file or window is sent to the speech synthesis server / TTS engine instead

Steps to reproduce

  1. Enter OSX System Preferences, select Accessibility, then Speech.
  2. Check the box "Speak selected text when the key is pressed"
  3. Click "Change key" to assign a key (e.g. Command+Option+Control+S)
  4. Enter some text into a new Sublime window or open an existing file. Select some or all text.
  5. Press the chosen hot key. The window title is spoken instead.
  6. Compare this to the behavior in nearly all other OSX apps -- Textpad, Stickies, Word, Safari, Chrome, Firefox, Emacs...

Environment

  • Operating system and version:
    • Windows ...
    • Mac OS: Sierra, El Capitan, Yosemite, and most likely earlier releases
    • Linux ...
  • Sublime Text:
    • Build 3126
@fabswt
Copy link

fabswt commented Nov 24, 2016

+1

@PhDeviate
Copy link

Several months later I would like to say, yes, please! This functionality would keep me from having to switch from Sublime to another text editor for certain tasks...

@keith-hall
Copy link
Collaborator

possible duplicate of #545

@keith-hall
Copy link
Collaborator

related: #3392 (comment)

@mrgrieves4
Copy link

Any possibility that this might get some attention? I'm a little horrified to see that this was raised in 2016.

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

No branches or pull requests

6 participants