From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: If bash can, why not Speakup?
Date: Thu, 18 Nov 2010 22:50:55 -0600 [thread overview]
Message-ID: <20101119045055.GA25302@linux1> (raw)
In-Reply-To: <98hbe0$4qqnq3@ipmail04.adl6.internode.on.net>
On Fri, Nov 19, 2010 at 12:52:38PM +1000, pj@pjb.com.au wrote:
> Janina Sajka wrote:
> > to track whether I'm in insert or command mode, i.e. it would
> > sure help if Speakup could give me a differently pitched voice
>
> Misunderstanding this to be about vim itself :-( , I wrote:
> > Presumably by writing something to somewhere in
> > /sys/accessibility/speakup/ (or /proc/speakup ?)
> > ... It might be possible to do it with a vim script
>
> And it is possible :-) if you copy spokenmode.vim (after the .sig)
> into your ~/.vim/plugin/ dir (you might have to mkdir it first)
> then you should see the contents of /tmp/t change according to
> the editing mode.
>
> It just remains to find something in /sys/accessibility/speakup/
> which switches between two suitable voices...
What you are going to be able to do with that is speech synthesizer
specific, so those settings are under the directory named by the
synthesizer name in /sys/accessibility/speakup.
For example on my desktop, the file to change the pitch is
/sys/accessibility/speakup/ltlk/pitch.
The values and their ranges are different for each synthesizer, so you
have to know the possible values and ranges to make them work correctly.
Also, some of them support relative pitch, so you can do things like
raise or lower the pitch by a specified amount.
William
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
pj
` William Hubbs [this message]
` Janina Sajka
-- strict thread matches above, loose matches on Subject: below --
Brian Buhrow
pj
pj
pj
` William Hubbs
` Albert Sten-Clanton
` Steve Holmes
` Gregory Nowak
` Steve Holmes
` Gregory Nowak
` Janina Sajka
` Janina Sajka
` Rynhardt Kruger
` William Hubbs
Janina Sajka
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=20101119045055.GA25302@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).