Hey John. I agree that something has happened between Emacspeak and Mac builds of Emacs starting with 29.1. I just wish I could fingerpoint what it is exactly. I did experience a similar issue, though I was not using and still do not the ignore-mac-accessibility flag. I wish I remembered the steps to get Emacspeak / Emacs combo into a working state though. It probablyinvolved the steps suggested by someone here, namely completely rebuilding Emacspeak repository, recompiling, and so forth. I wish we had the list of all the dependencies that Emacspeak relies on that could affect Emacs's behaviour. One interesting behaviour I've been struggling with has to do with the unpredictable delay when Emacspeak starts. To be more precise, it does start, but nothing is spoken for a few seconds when moving up and down arrows even though I later see the "next line" and "previous line" messages in the Messages buffer (after Emacspeak is back to normal). I know all of the above does not sound convincing until we can figure out a way to log the session. Anyway, in your particular case, can you double-check if other Emacspeak shortcut keys produce spoken feedback after you hear the "welcome" message? > On Jan 31, 2024, at 3:19 PM, John Covici <emacspeak@xxxxxxxxxxxxx> wrote: > > So, by setting ignore-mac-accessibility to nil, I was able to get > enough speech without emacspeak running to do eval and load the setup > file. After I loaded it did say welcome to emacspeak, but emacs > became non functional as previously reported. > >> On Wed, 31 Jan 2024 08:04:51 -0500, >> Parham Doustdar (via emacspeak Mailing List) wrote: >> >> [1 <text/plain; utf-8 (quoted-printable)>] >> Also, if mplayer ends up not being the issue, can you clarify what you mean by “some sort of fatal error”? What sort? :-) Also, any tracebacks? >> >>>> On 31 Jan 2024, at 13:40, John Covici <covici@xxxxxxxxxxxxxx> wrote: >>> >>> Thanks for your quick response. >>> >>> I did make clean, make confiig and make whenever I changed the >>> emacspeak I was using. I did tryy to load emacspeak using esc-x >>> load-file, but I got some kind of fatal error when trying to do that. >>> Since this is a mac, would I need mplayer and sox? >>> >>> On Wed, 31 Jan 2024 06:36:08 -0500, >>> Parham Doustdar (via emacspeak Mailing List) wrote: >>>> >>>> [1 <text/plain; utf-8 (quoted-printable)>] >>>> Hi John, >>>> There could be many reasons for this, so I’m going to throw a whole bunch of steps at you to see which one works, haha. >>>> First, have you tried running `make clean` and `make` when you either go back to a release or to the git HEAD? >>>> Also, do you have Emacspeak dependencies, notably mplayer and sox installed? >>>> If you do all this, we’ll need to figure out what happens when you load Emacspeak. I’m not sure of the best way to do this given your configuration, but maybe try the emacs -Q that you did before, and do M-: (load-file “~/src/emacspeak/lisp/emacspeak-setup.el”) or whatever your emacspeak path is, and see if you can read the buffer contents with the errors, maybe from th e*Messages* buffer. >>>> Hope this gives you a few next steps to debug the issue! >>>> >>>>> On 31 Jan 2024, at 12:28, John Covici (via emacspeak Mailing List) <emacspeak@xxxxxxxxxxxxx> wrote: >>>>> >>>>> Hi everyone. So, I think this started after upgrading to emacs 29.1. >>>>> What happens is that after emacspeak is loaded emacs does not work -- >>>>> escape followed by x types x in the buffer. c-x followed by b does >>>>> nothing at all. Many other things don't seem to work as they should. >>>>> >>>>> So, I started on the hunt. I am using the railway casc out of >>>>> homebrew, but the same thing happens with the original emacs macport. >>>>> So, the first thing I did was from the terrminal typed >>>>> /opt/homebrew/Cellar/emacs-mac/emacs-29.1-mac-10.0/Emacs.app/Contents/MacOS/Emacx >>>>> -q to see if it was my settings. Sure enough, emacs was functioning, >>>>> I knew this because vo read some things and I could actually hear m-x >>>>> when I typed esc-x . So, I then fooled around with my .emacs file and >>>>> sure enough, the load of emacspeak was the problem. I was using >>>>> emacspeak from git and I went back to emacs 59, but no joy. I am >>>>> stumped after that, so any suggestions as to how to debug further >>>>> would be appreciated. >>>>> >>>>> Thanks all. >>>>> >>>>> -- >>>>> Your life is like a penny. You're going to lose it. The question is: >>>>> How do >>>>> you spend it? >>>>> >>>>> John Covici wb2una >>>>> covici@xxxxxxxxxxxxxx >>>>> Emacspeak discussion list -- emacspeak@xxxxxxxxxxxxx >>>>> To unsubscribe send email to: >>>>> emacspeak-request@xxxxxxxxxxxxx with a subject of: unsubscribe >>>> >>>> [2 <text/plain; UTF-8 (8bit)>] >>>> Emacspeak discussion list -- emacspeak@xxxxxxxxxxxxx >>>> To unsubscribe send email to: >>>> emacspeak-request@xxxxxxxxxxxxx with a subject of: unsubscribe >>> >>> -- >>> Your life is like a penny. You're going to lose it. The question is: >>> How do >>> you spend it? >>> >>> John Covici wb2una >>> covici@xxxxxxxxxxxxxx >> >> [2 <text/plain; UTF-8 (8bit)>] >> Emacspeak discussion list -- emacspeak@xxxxxxxxxxxxx >> To unsubscribe send email to: >> emacspeak-request@xxxxxxxxxxxxx with a subject of: unsubscribe > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici@xxxxxxxxxxxxxx > Emacspeak discussion list -- emacspeak@xxxxxxxxxxxxx > To unsubscribe send email to: > emacspeak-request@xxxxxxxxxxxxx with a subject of: unsubscribe
|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.