From: "Chris Norman" <cnorman@rnibncw.ac.uk>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: backspace bleep problem solved
Date: Thu, 4 May 2006 08:09:46 +0100 [thread overview]
Message-ID: <004001c66f49$b9ec6190$7300a8c0@sparky> (raw)
In-Reply-To: <20060503141915.GE5412@lnx3.holmesgrown.com>
How do you save settings?
Cheers,
Chris Norman
<!-- chris.norman4@ntlworld.com -->
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 03, 2006 3:19 PM
Subject: Re: backspace bleep problem solved
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Thanks Dude. Note that option could be saved permenantly like the other
> /proc/speakup settings too. The name of that variable gave me an idea
> to speculate. I wonder if somehow, Speakup is having some trouble
> tracking correct attribute changes.
>
> On Wed, May 03, 2006 at 03:49:18AM -0400, Joshua Lambert wrote:
>> I got rid of annoying backspace bleep by:
>> echo 0 > /proc/speakup/attrib_bleep
>> It still gives the helpful beeps while moving through a document and the
>> top and botom edge of a screen but shuts down the annoying backspace
>> beeping.
>> Cheers,
>> Josh
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>
> - --
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.7 (GNU/Linux)
>
> iD8DBQFEWLvjWSjv55S0LfERA1C7AJ9p37TvRZSA7cJIIFbe9j0J+QCb/gCg0dzT
> ZKHh8WncTwPl5k1lm53pE6g=
> =RLiV
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Joshua Lambert
` Steve Holmes
` Chris Norman [this message]
` ace
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='004001c66f49$b9ec6190$7300a8c0@sparky' \
--to=cnorman@rnibncw.ac.uk \
--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).