From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: High-Frequency at The Bottom?
Date: Sat, 12 May 2007 23:24:15 -0700 [thread overview]
Message-ID: <20070513062415.GA20850@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSF.4.64.0705122222240.45617@server2.shellworld.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you're talking about the beeps your pc speaker makes, then this is
the expected behavior. The lower down on the screen you are, the
higher the pitch of the beep speakup produces.
Greg
On Sat, May 12, 2007 at 10:30:36PM -0700, Hart Larry wrote:
> Well, on Saturday I had some1 helping here--and we finally got more than
> 25-lines on this screen. It seems amazing that pine-and-lynx just keep
> displaying until all 48 of these lines are filled. Well, now that I have
> 48-lines, as I am useing speakup review, when I get to the bottom, the sound
> has become much higher. The sound at the top on line 1 is normal--and I looked
> in the /proc/speakup dir, but find nothing which changes the frequency of this
> tone
> Thanks in advance for any suggestions
> If I were guessing, maybe the tone is 8KHZ?
> Hart
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGRq8P7s9z/XlyUyARAsdbAKCiUbkucmBVqR4QRC+yEa3GJ0TMxwCeOfcv
bHA0dLVSUlUu1n8mIYibmRw=
=HzXp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Hart Larry
` Gregory Nowak [this message]
` Chris Norman
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=20070513062415.GA20850@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).