Chuck: I have come to the same conclusion about speakup initialization, but with a twist. Because I use more than one synth at one time or another, I think it useful to create synth specific directories in /etc/speakup, e.g. /etc/speakup/ltlk, /etc/speakup/bns, etc. I have not implemented this yet, though, because I'm not quite smart enough yet with shell scripts to read in the value of /proc/synth and use that value to trigger sourcing the appropriate subdirectory of /etc/speakup. I know it's not a rocket science level of bash scripting to do that, I just haven't gotten there yet. My second suggestion relates to where to put the script/alias. I would think it belongs in /home/$USER/.bash_profile. That way, the machine can be shared with folks in the household/office who don't use speech, and it can be accessed across the net (as I do with my notebook at home from my workstation at my office) without triggering the chatter and scarring the cleaning lady. On Fri, 11 Jan 2002, Charles Hallenbeck wrote: > Initializing speakup (or reinitializing it) is so simple from a > shell prompt that it probably is not worth making it a speakup > builtin feature. With a little preparation first, which I will > explain in a moment, it can be done with a command like this (the > "-R" is upper case): > > cp -R /etc/speakup /proc > > You could further simplify that command by creating a very short > script or even using an alias. > > The preparation involves first creating an appropriate > /etc/speakup directory that can just be copied wholesale into > /proc/speakup, but that only needs to be done once. Here is how I > did it: > > First, issue the following command: > > cp -R /proc/speakup /etc > > Now you have an exact copy under /etc/speakup of what started out > in /proc/speakup, but there is more to do. The problem is that > some of the "files" under /proc/speakup are read-only and others > are read-write, and you have to find out which is which and > eliminate the read-only elements under /etc/speakup. Once you do > that, the command I gave earlier is ready to go. > > I have included the initialization command in my rc.local file > and also in /etc/profile. This may sound redundant, but there > have been times when putting it only in rc.local has failed to > work because the synth was busy speaking bootup messages when the > command was executed. The repetition in /etc/profile is > insurance, and it also lets me reinitialize the synth each time I > log into a new account, or reenter once I have been using. > > Chuck > > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>* > Visit me at http://www.mhonline.net/~chuckh > The Moon is Waning Crescent (4% of Full) > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina at afb.net Phone: (202) 408-8175 Chair, Accessibility SIG Open Electronic Book Forum (OEBF) http://www.openebook.org
