-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Integrate Emacspeak into Doom, or support Emacspeak #4256
Comments
Hello, I figured that I would take a stab at this since I too enjoy using emacs and use Emacspeak. I will put in my packages.el file, as well as the error that I get when I run doom sync. packages.txt |
So I did try to use Doom with Emacspeak after compiling it by hand, and unfortunately I am not sure what else would need to go into getting this to work. When I launch Emacs after adding the load-file call to my ~/.doom/config.el, Emacspeak says the espeak version message but nothing thereafter. @devinprater did you try this also, and if so, what did you discover? |
Sorry, I've not tried it. I just stuck with vanilla Emacs with my config
file, while I was still on Linux.
|
Just in case it helps anyone. I was able to get Emacspeak basically working under doom by doing the following -
(add-hook 'after-init-hook (load (expand-file-name "./my-emacspeak.el")) I found the after-init-hook was required because otherwise, you got errors relating to problems with Emacsepak trying to remap the C-e key (emacspeak uses C-e as a prefix command and remaps end-of-line to C-e e and C-e C-e). There are still some problems to fix up. I notice some text does not get spoken which should and imagine there are a few doom functions which will probably need emacspeak advice added to them. However, this does get a basic install sort of working. |
I will have to try this; when I tried it by hand, I couldn't get the modifications I made to rate to stick until I restarted Doom, but that caused further issues because I got messages about how the device was not a terminal. |
Do you have a gist of step three? Will give Doom another look and kick the tires again. |
I think I have the basics of doom and emacspeak working together (although not in an ideal way and not enough to solve this issue). I have tested these steps in this environment:
Steps:
emacspeak & Before I got my emacspeak installation working, emacspeak would sometimes play a welcome announcement but then not say anything else. Based on symptoms, I think the initial announcement might be a recording that doesn't actually use the engine. I see @hjozwiak had the same problem. For me this was independent of Doom's involvement. I can't remember which thing fixed it, but among other things, I used Anyway, after it launches, navigate around a little and make sure it reads something related to what you navigated over before you bring Doom into the mix. Debug if it does not.
git clone --depth 1 --single-branch https://github.com/doomemacs/doomemacs ~/.config/emacs Make sure ln -s ~/.config/emacs ~/.emacs.d If .emacs.d already exists, you'll have to sort the situation as you see fit. Finally: export PATH=$PATH:$HOME/.config/emacs/bin
doom install I did not have it create an envvar file.
emacspeak & Edited to insert a new step 5:
I don't think even this much was working in 2022-11, and it's possible I did something system-wide then (beyond setting emacspeak's speech engine) that I didn't write down. I am new to both doom and emacspeak, and am returning to emacs after a 22 year gap, so I might not know what is supposed to happen, and I might not see all the relevant error messages. Verification by someone else, particularly someone who has used at least one of these packages, particularly on a fresh system, would be much appreciated. Ideally, I would like both doom and emacspeak to load when one launches emacs via any method. That is what I will try to set up next, using the hints from @theophilusx earlier in this ticket. I dug into the emacspeak launch setup quite a bit before I got it to work, so I think I can construct a |
I managed to get Emacspeak working inside Doom-Emacs with the following steps:
I'm not blind or have any vision problems, but I was curious about trying out Emacspeak since I thought it could be a way to continue working at the computer without excessively straining my eyes. While Emacspeak is working correctly in Doom-Emacs as far as I can tell, it would take some time to get used to all the keybindings and speaking that it does, much like everything else there is to learn in technology. It will be really nice when an Emacspeak module is created for Doom. Sometime it speaks too much (e.g. telling me whenever I switch between the normal, visual, and insert minor modes) or too little in my opinion, and I also wish it would speak different things at different rates. It would also be convenient if there was the ability to easily turn Emacspeak on or off whenever I want with a keybinding, but I haven't figured out how to turn Emacspeak off when it's already turned on after evaluating |
Describe the feature
functionality is better?
Emacspeak is a speech system for blind people that turns Emacs into an "auditory desktop." It uses speech, speech characteristic changes, and sounds to convey information, using system TTS functions (Linux: ESpeak (free) or Outloud($5)), Mac (say command). I'm not sure how well it could be integrated into Doom, but it would be nice to have a good, easier-to-use version of Emacs I just point people to, that would actually work well for them, rather than just having to say "Well you can use Emacs, but you have to fiddle with it for hours so you might as well use VS Code if you want to be productive." Emacspeak isn't in any other distribution of Emacs, as far as I know. Emacspeak doesn't replace any other feature. It is loaded using Load-file, so it's not really like packages that are on MELPA. It doesn't have a command to start it, although a doom script could be added to switch it on or load it into the .emacs.el.
I've not tried Doom yet, but I'll update this issue when I have, and if Emacspeak does work it it, just being put into the .emacs.el. I usually use a Windows PC, but Emacspeak for Windows is pretty out of date, so I'll use a MacBook Pro, late 2019 with four thunderbult ports, for this.
The text was updated successfully, but these errors were encountered: