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: how to tell which synthesizer is active
Date: Sun, 13 Sep 2009 12:29:19 -0500	[thread overview]
Message-ID: <20090913172919.GA15752@linux1> (raw)
In-Reply-To: <20090908194218.GA19578@romuald.net.eu.org>

Hi Greg,

On Tue, Sep 08, 2009 at 12:42:18PM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> How about a compromise? I propose leaving synth as is, and creating a
> new file, /sys/accessibility/speakup/synth_active, which would be a
> boolean. If the value is 1, the synth is active. If the value is 0,
> the synth has timed out/prtscr was pressed to turn the synth off. This
> way, synth can stay as is, and active could be checked in scripts, to
> decide what action could be taken. So, for example, if synth is set to
> bns, and active is set to 0, then you'd know that a hardware synth is
> in use, but that it isn't attached. How does that sound, and could it
> be implemented?
 
 I can look into something like this.  How about putting it in the synth
 directory though, such as /sys/accessibility/speakup/bns/active?

William


  reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 covici
 ` Tony Baechler
   ` How to Tell Which Synthesizer is Active? Hart Larry
     ` Tony Baechler
   ` how to tell which synthesizer is active covici
     ` William Hubbs
       ` covici
         ` William Hubbs
           ` John G. Heim
             ` William Hubbs
           ` Gregory Nowak
             ` William Hubbs [this message]
               ` covici
               ` Gregory Nowak

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=20090913172919.GA15752@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).