Open jsholmes opened 5 years ago
Hi @jsholmes,
If memory serves, I recall the install working as expected with Mojave. Judging by the console output, your environment requires your permission to write to your ~/Library/Services
directory. You can complete the installation process (manually) by copying ~/.emacs_anywhere/Emacs Anywhere.workflow
to ~/Library/Services
. Then, you should be ready to proceed as per usual and assign a keyboard shortcut to the service as described in the README
.
Thank you for bringing this issue to our attention, @jsholmes. And, feel free to let us know if the steps I have prescribed do, or do not work for you.
If anyone else runs into the issue that @jsholmes has, leave a comment. I'll accept a pull request mentioning this issue in the README
.
Go with Emacs, Z
Hey there, I'm trying it with Spacemacs and it half-works. Currently on Catalina, 10.15.1, Spacemacs Dev 0.3 latest build (it changes all the time so whatever is current since the last day or two or three), using Firefox 70.0.1 to test input.
I set my keystroke to control-shift-E in the system preferences after installing emacs-anywhere with curl (no problems there). I then tried the keystroke in this input text area (and others such as twitter input) and it doesn't work. If I do it via menu Firefox > Services> Emacs Anywhere, it will pop up the Emacs/Spacemacs buffer just fine, but when I type something, and hit SPC F d (to quit the buffer), I get the following:
The action “Run Shell Script” encountered an error: “161:177: execution error: System Events got an error: osascript is not allowed assistive access. (-25211) 52:64: execution error: System Events got an error: osascript is not allowed assistive access. (-1719) 36:68: execution error: System Events got an error: osascript is not allowed to send keystrokes. (1002)”
As a pop-up after the buffer disappears.
Not exactly sure what to do or what's wrong. I googled and it appears to of course be some sort of permissions error, but unsure as to the remedy as of yet. Just wondering if you had any ideas.
Thanks for any info!
@NatHarari for your issue you need to make sure that Script Editor
is in
System Preferences > Security & Privacy > Privacy > Accessibility
if not, add it, Script Editor
is in /Applications/Utilities/Script Editor.app