public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Steve Holmes <steve@holmesgrown.com>
To: speakup@linux-speakup.org
Subject: Re: how to make settings 'stick'
Date: Sun, 28 Dec 2014 10:11:46 -0800	[thread overview]
Message-ID: <20141228181146.GA577@linlap> (raw)
In-Reply-To: <20141226205535.GA25662@Enterprise>

I have those all in place, I've used speakupconf for years; It's just
recently, that the parms don't change when I run the script. I should
clarify a bit more on this. When I run speakupconf from command line
in normal user, speakup parms do not change and I get no errors. But
if I manually echo "7" to /sys/accessibility/speakup/soft/rate, I get
an error message saying that permission is denied. So I figure if
these permissions aren't right, then speakupconf won't work either.

Is this clearer now?

On Fri, Dec 26, 2014 at 03:55:35PM -0500, Doug Smith wrote:
> I think what he is trying to do is to echo the settings into the /proc/speakup or whatever they are called parameters.  You are right.  If he would 
> use speakupconf he would have no difficulties.  I have speakup working on a fully updated sonar linux system which is the same, basically, as a 
> working arch system and all I had to do when trying to set speakup parameters the way I wanted them was to just adjust the volume, speed and whatever 
> other settings I wanted the way I wanted them then do this: 
> 
> speakupconf save
> 
> This will put a .speakup directory into his home folder and allow him to append the following to his .bashrc file: 
> 
> speakupconf load
> 
> When he logs in, all the parameters will be set back the way he wants them.  
> 
> 
> 
> Hope this helps and happy New Year.
> 
> 
> 
> 
> -- 
> Doug Smith: Special Agent
> S.W.A.T  Spiritual Warfare and Advanced Technology
> Forever serving our LORD and SAVIOUR, JESUS CHRIST.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

      reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 David
 ` Rob Hudson
   ` David
   ` Steve Holmes
     ` Chuck Hallenbeck
       ` Steve Holmes
         ` Chuck Hallenbeck
         ` Doug Smith
           ` Steve Holmes [this message]

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=20141228181146.GA577@linlap \
    --to=steve@holmesgrown.com \
    --cc=speakup@linux-speakup.org \
    /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).