Glad to hear you got it working. However, I don't believe you need to do another install. From memory, by default, the startup sounds/theme is disabled. You can enable it by setting emacspeak-play-emacspeak-startup-icon to t in your .emacs (or via customize if your emacspeak startup script does not short-circuit that mechanism by loading .emacs 'manually'). With the auditory icons, a bit depends on your setup and it may require some configuration. You can try issuing the command M-x emacspeak-toggle-auditory-icons to see if they are turned on or not. If they are on and you still don't hear them, it is likely you need to configure the shell program used to play them. Also, by default, I think the installation process only installs the default sound theme. If you want to use one of the other themes, you may need to install the files manually. Note however, its been a long time since I've used emacspeak's installation process, so I could be wrong or things may have changed. The one thing I'm pretty sure about is that re-installing is unlikely to change anything (at least not in a positive way). The things which are not working quite write from here on are most likely configuration issues rather than build issues. Tim Jude DaShiell writes: > Now when I run emacspeak I get emacspeak up speaking the emacs screen > that happened after those permissions ggot fixed. There used to be some > organ notes that played before emacspeak started speaking but those > don't yet play on this computer. I may have to do another make and make > install somewhere to enable audio icons. > > On Mon, 9 May 2011, Tim Cross wrote: > > > My guess would be that the espeak tcl script in the servers directory did > > not have the execute permission set. You either have to do a chmod u+x > > espeak or run it with tcl explicitly i.e. tcl espeak. The make install > > probably updates the execute permission as part of the install process, > > which would explain why you can run it now. > > > > I don't use the emacspeak script. Originally, it use to prevent the > > automatic loading of the users .emacs file in order to make sure the > > emacspeak stuff was loaded first and then it would manually load .emacs. > > However, this use to cause issues with using the customize interface. I > > think this has all changed now, but I'm use to using my own setup file which > > I call from the top of my .emacs, so I can just run emacs > > > > Tim > > > > > > > > On Mon, May 9, 2011 at 12:11 PM, Jude DaShiell <firstname.lastname@example.org>wrote: > > > > > That espeak script wouldn't allow me to run it even as root earlier, > > > however, emacspeak -e <cr> does bring up emacspeak speaking. So I think > > > I'm on the home stretch by now.On Mon, 9 May 2011, Tim Cross wrote: > > > > > > > > > > > Hi Jude, > > > > > > > > what you have done is not correct. The tclespeak.so file is loaded by the > > > > espeak script. The DTK_PROGRAM should be set to espeak NOT tclespeak. > > > > > > > > I never do make install for emacspeak as I prefer to keep it all in > > > directories > > > > under my home directory. What you should try, before doing any make > > > install and > > > > after doing make in the linux-espeak directory is > > > > > > > > 1. Check that the espeak script in the servers directory is executable > > > > 2. Just run this script and you should hear it speak via espeak. You can > > > use > > > > control d to exit or you can use normal espeak TTS commands to queue and > > > then > > > > speak more text (see the emacspeak main Makefile for a description). If > > > that > > > > all works, then you know that the espeak emacspeak server works. If you > > > then > > > > run make install, you may need to track down paths and permission issues, > > > but > > > > at least you know the server and synthesizer do work with the versions of > > > tcl > > > > you have etc. > > > > > > > > Tim > > > > > > > > Jude DaShiell writes: > > > > > not compatible and here's why. The make install puts a directory in > > > > > /usr/share/emacs/site-lisp/emacspeak/servers/linux-espeak/ which has > > > only > > > > > one file in it called tclespeak.so. I changed DTK_PROGRAM to > > > tclespeak > > > > > and emacspeak still leaves error message file to attach to process is > > > a > > > > > directory. Now why that happens is above my pay grade to answer. > > > > > > > > > > > > > > > > > > ----------------------------------------------------------------------------- > > > > > To unsubscribe from the emacspeak list or change your address on the > > > > > emacspeak list send mail to "email@example.com" with a > > > > > subject of "unsubscribe" or "help". > > > > > > > > > > > > > > > > > > > > > > > > > ----------------------------------------------------------------------------- > > > To unsubscribe from the emacspeak list or change your address on the > > > emacspeak list send mail to "firstname.lastname@example.org" with a > > > subject of "unsubscribe" or "help". > > > > > > > > > > -- Tim Cross Information Technology University of New England Phone: +61 2 6773 3210 Mobile: 0428 212217 Fax: +61 2 6773 3424 E-Mail: email@example.com Web: http://www.une.edu.au/itd --- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Any fool can make things bigger, more complex, and more violent. It takes a touch of genius (and a lot of courage) to move in the opposite direction. âAlbert Einstein ----------------------------------------------------------------------------- To unsubscribe from the emacspeak list or change your address on the emacspeak list send mail to "firstname.lastname@example.org" with a subject of "unsubscribe" or "help".
If you have questions about this archive or had problems using it, please send mail to:email@example.com No Soliciting!
Emacspeak List Archive | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | 1998 | Pre 1998
Emacspeak Files | Emacspeak Blog | Search the archive