| Hi Victor I’ve done some more investigating, completely stripped back my init file and tried messing around with some emacspeak internals to no success. I believe the latest macOS update has somehow broken how swiftmac responds to events or is queuing what to say, even the dtk-stop command doesn’t seem to work for several seconds if I move around certain buffers rapidly. For example, if starting at the top of the default scratch buffer, if I press C-n C-p for around 10-20 times in rapid succession, emacspeak will repeat ;; several times before doing anything else as if each line has been queued and takes a second or so for it to process there’s new text to announce. If I go to the end of that same buffer however and type several of my own lines then repeat the same process with the new lines, it will will not buffer like that and will respond immediately if I navigate else where. While this specifically isn’t a major issue, similar things occur when rapidly navigating through code or switching buffers with ido where it is an issue. I’ve reverted to using the old Mac speech server which does not have the same issue however it does generally feel slightly slower which is why I started using the swiftmac server previously. I also tried using the latest swiftmac server downloaded from the GitHub page however was unable to select any voices successfully other then the default low quality one and it seemed to have the same issue with some speech seemingly being queued no matter what. To confirm, I’m on macOS 26.3.1 I’m not really sure where to go from here but any help would be greatly appreciated. Best Regards, Isaac P.S. Also I’m not sure why but it seems like my emails are now using my google username rather then my actual name, not sure how to fix that sorry.
|
|Full archive May 1995 - present by Year|Search the archive|
If you have questions about this archive or had problems using it, please contact us.