I'm just getting started with emacsspeak, and I spent quite some time that after building the project with make config && make and running a ./runq my Emacs movement is broken. For example, pressing backspace would not delete a character in a buffer or minibuffer, instead it gets ignored.
I turned out to be my bad of not having read further section about having to also build servers/native-espeak. However, I think having at least some error message in the minibuffer and *Messages* would help with debugging potential situation where for whatever reason the DTK_PROGRAM is not working.
Steps to reproduce
Build project with make config && make
Make sure native-espeak is absent, in particular make clean -C servers/native-espeak
Run unset DTK_PROGRAM; ./runq. At this point Emacs is not supposed to pronounce anything because DTK_PROGRAM is missing.
I'm just getting started with
emacsspeak
, and I spent quite some time that after building the project withmake config && make
and running a./runq
my Emacs movement is broken. For example, pressingbackspace
would not delete a character in a buffer or minibuffer, instead it gets ignored.I turned out to be my bad of not having read further section about having to also build
servers/native-espeak
. However, I think having at least some error message in the minibuffer and*Messages*
would help with debugging potential situation where for whatever reason theDTK_PROGRAM
is not working.Steps to reproduce
make config && make
make clean -C servers/native-espeak
unset DTK_PROGRAM; ./runq
. At this point Emacs is not supposed to pronounce anything becauseDTK_PROGRAM
is missing.*Messages*
buffer and read its contentExpected
There's an error about
DTK_PROGRAM
not workingActual
There's no error