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

Accessibility: Dashboard cannot be used with Emacspeak #295

Closed
devinprater opened this issue Feb 17, 2021 · 4 comments
Closed

Accessibility: Dashboard cannot be used with Emacspeak #295

devinprater opened this issue Feb 17, 2021 · 4 comments
Labels

Comments

@devinprater
Copy link

Hello. I am a blind person, and use Emacspeak to use Emacs (on arch Linux, Emacs version GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.22, cairo version 1.17.3) of 2020-08-28)

I installed Dashboard with Melpa, and used:

( require   'dashboard )
(dashboard-setup-startup-hook)

to initialize it on startup. But, using Emacspeak, pressing C-n and C-p don't work. Looking further, it turns out Dashboard-mode has its own previous-line and next-line commands. I'm not a programmer, so I can't really say how to fix this, but what Emacspeak usually does is use Advise to speak info, like in Emacspeak-dired. I hope this helps, and thanks so much for the package!

@jcs090218
Copy link
Member

Hi @devinprater. You can use arrow keys to navigate through the dashboard buffer. We do have the proposal at #187. Let me know if the need anything else! :)

@devinprater
Copy link
Author

The problem is that neither "dashboard-next-line" nor "dashboard-previous-line" work with Emacspeak. So none of the keys bound to those commands result in the items moved to being spoken by Emacspeak.

@jcs090218
Copy link
Member

Not sure if I understand your question. Would next-line and previous-line command work in Emacspeak? If so, try override the key binding like the following snippets.

(define-key dashboard-mode-map (kbd "C-p")  #'previous-line)
(define-key dashboard-mode-map (kbd "C-n")  #'next-line)

@jcs090218
Copy link
Member

I think the issue can be closed? Feel free to reopen it if you still having issue. :)

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

No branches or pull requests

2 participants