public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Broken Paramaters in Speakup
Date: Mon, 20 Oct 2008 09:11:43 -0500	[thread overview]
Message-ID: <20081020141143.GA19140@linux1> (raw)
In-Reply-To: <20081017222404.GA4317@lnx3.holmesgrown.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

I have just committed a change to git that removes most of the error
messages.  Can someone pull from git and reply to this thread and let me
know  how it is working now?

Thanks,

William

On Fri, Oct 17, 2008 at 03:24:05PM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> I was thinking of doing something like that.  I figured I would report
> it here so we can see if it can be fixed or if someone can tell me
> where to look, I might even take a stab at it.  I've never dealt with
> kernel control variables before.  But your solution is a good
> work-around for the time being.
> 
> On Fri, Oct 17, 2008 at 05:39:44PM -0400, Chuck Hallenbeck wrote:
> > Steve,
> > 
> > I hope someone smarter than me can figure that one out. I had to kludge
> > a partial solution like this:
> > 
> > 1. forget about the speakupconf save function. Also forget about normal
> > users being able to update the parameters. Limit it to root.
> > 
> > 2. Start with an inherited copy of /etc/speakup/ if you are lucky
> > enough to have one, and make any necessary changes to its contents with
> > an editor.
> > 
> > 3. run speakupconf load, note which files produce errors, and delete
> > them from /etc/speakup/
> > 
> > The result is that the files that remain in /etc/speakup/  will work
> > okay with speakupconf load, and that's as good as it's going to get.
> > I'm sure there's a better solution, but the above is how I'm surviving
> > until the Cavalry comes.
> > 
> > Chuck
> > 
> > 
> > On Fri, Oct 17, 2008 at 12:55:14PM -0700, Steve Holmes wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: RIPEMD160
> > > 
> > > With the version of speakup in the 2.6.26-1 kernel, I find that some
> > > of the variables or files in /sys/module/speakup/parameters/ won't
> > > update properly.  3 examples are the punc-some, punc-most and punc_all
> > > variables.  What happens is if you cat the values from a saved place
> > > such as is done with speakupconf, I get a slew of errors saying "cat:
> > > argument invalid" and the targets end up empty so what happens in my
> > > case is the punc_most chars get completely whiped out.  I also get
> > > this error if I try and cat that variable by hand so the script is ok
> > > here.
> > > 
> > > Also, when I do a speakupconf save I get the errors I'll show below.
> > > I'm using spkout as the synth of choice.
> > > Script started on Fri 17 Oct 2008 06:58:17 AM MST
> > > lnx3:~# speakupconf save
> > > cp: omitting directory `.'
> > > cp: reading `voice': Invalid argument
> > > cp: reading `lang': Invalid argument
> > > cp: reading `freq': Invalid argument
> > > cp: reading `silent': Operation not permitted
> > > lnx3:~# exit
> > > exit
> > > 
> > > Script done on Fri 17 Oct 2008 06:58:39 AM MST
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.9 (GNU/Linux)
> > > 
> > > iEYEAREDAAYFAkj47aEACgkQWSjv55S0LfHY4wCdEqpX0fx8Jp1p80z/kkN8/2VP
> > > eZgAoOIf8Evgs7+1wX9XffOViKYiqMm4
> > > =ZqSR
> > > -----END PGP SIGNATURE-----
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > -- 
> > The Moon is Waning Gibbous (87% of Full)
> > 
> > My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022.
> >                                 --------
> > Sarah Palin: At last, a Beauty Queen who doesn't want World Peace.
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> 
> iEYEAREDAAYFAkj5EIQACgkQWSjv55S0LfFvwACfZp6I9R6r8mR+PN0iPPTnMh+g
> Ny4AnjZo0AHBx7CCx6o3ciWyyhh7rJnE
> =sUBk
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkj8kZ8ACgkQblQW9DDEZTjtOwCgvSK8d2VwW0+ANnzER9MsU+oP
JZgAn323i137j3nL8xPgpV8yAk+NXkj5
=np7y
-----END PGP SIGNATURE-----

  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Steve Holmes
 ` Chuck Hallenbeck
   ` Steve Holmes
     ` William Hubbs [this message]
       ` Steve Holmes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081020141143.GA19140@linux1 \
    --to=w.d.hubbs@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).