Re: Configuration Files

[Ryan Mann <rmann@rmisp.net>]

For a more key word-like configureation file option, you might want to
look at my Speakup -utils package.  You can put something like;
rate 9
volume 4
end
in /etc/speakupctl.conf and run "speakupctl restore"
You can download this package at
ftp://ftp.linux-speakup.org/pub/linux/goodies/speakup-utils.tar.gz.




Ryan

It's better to make a difference than to make a million.


On Fri, 28 Feb 2003, Luke Davis wrote:

> That is good, and gives me an interesting idea, which I will investigate.
>
> However, I would still like your opinion re what I wrote earlier.  Would a
> unified, more free-form (keyword value option <nl> keyword value option),
> type config file or interface, be of more use to you, and as such would it
> be worth my time investigating?
>
> Thanks
>
> Luke
>
>
> On Fri, 28 Feb 2003, Chuck Hallenbeck wrote:
>
> > Here is how I do it:
> >
> > I maintain a directory under /etc called speakup which contains
> > all the elements of /proc/speakup which are configurable. Some
> > elements under /proc/speakup are not configurable; they are
> > read-only. But such things as rate, pitch, punc_level, and the
> > strings for some and most punctuation, can be written as well as
> > read.
> >
> > I have a command in my /etc/rc.d/rc.local, and again in
> > /etc/profile, like this:
> >
> > cp -R /etc/speakup /proc
> >
> > so that on bootup and whenever a user logs in, speakup is
> > configured to whatever the values are in the /etc/speakup
> > directory.
> >
> > So to change something I must either write the new value to
> > /proc/speakup, or else edit the stuff in /etc/speakup and then
> > execute a command such as shown above.
> >
> > This is not particularly user friendly either, but it is a good
> > starting point. I believe Janina and others who use more than one
> > synth from time to time have worked out an even more elaborate
> > but more flexible method of saving and restoring speakup
> > parameters.
> >
> > HTH -
> >
> > Chuck
> >
> > On Fri, 28 Feb 2003, Luke Davis wrote:
> >
> > > Useful knowledge, which I previously did not have.
> > >
> > > So should all configuration be handled this way, thus making a
> > > configuration file approach meaningless, or is there still potential for
> > > value to that idea, either now or for future configurable options?
> > >
> > > I don't particularly mind writing values to /proc entries every time I
> > > want to change the punctuation level, but I am not all users, and some
> > > might want a more intuitive way of handling this, such as an rc or other
> > > such file.
> > >
> > > I would like any opinions I can get.
> > >
> > > Luke
> > >
> > > On Fri, 28 Feb 2003, Chuck Hallenbeck wrote:
> > >
> > > > Speakup presently allows punctuation level to be set at none,
> > > > some, most, or all. The some and most levels can be configured by
> > > > the user to include or exclude whatever he or she wishes. You
> > > > select the level by writing a number to /proc/speakup/punc_level,
> > > > and you can edit and rewrite the some and most strings to that
> > > > directory too. I am not sure what other functionality would be
> > > > added by Luke's suggestions. Maybe I am misunderstanding
> > > > something, but it seems to me the existing features will do
> > > > pretty much whatever one wishes.
> > > >
> > > >
> > > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>