From: "Rob Hudson" <captinlogic@gmail.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: some semi technical questions
Date: Thu, 26 Dec 2013 12:21:59 -0600 [thread overview]
Message-ID: <C13A5884A1EC4BD2A0544819DDB8A44D@windows3f8340d> (raw)
In-Reply-To: <alpine.LNX.2.03.1312261253500.6407@ftml.net>
Irssi already does that. What I am working on is better channel and message
level control for what you hear, not what is displayed.
For instance, with this script, you will be able to monitor more than one
channel at once, without having to pin windows to each other, eg.
/join -window #channel
You will also have the ability to turn off windows, disable speech entirely
without turning off speakup, have long url's shortened *ever seen an ebay
link?) and a few other nifty things. You
----- Original Message -----
From: "Chuck Hallenbeck" <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Sent: Thursday, December 26, 2013 12:02 PM
Subject: Re: some semi technical questions
> On Thu, 26 Dec 2013, Rob Hudson wrote:
>
>> Would it be better to have the scripts send messages to something like
>> speech-dispatcher, or can messages be queued and sent directly to speakup
>> itself?
>
> Why not just have your script send messages to the screen and let the
> screen reader handle them?
>
>
>
>
> --
>
> Chuck, now in Ghent: (northeast of Hudson on the Hudson)
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Rob Hudson
` Samuel Thibault
` Chuck Hallenbeck
` Rob Hudson [this message]
` Janina Sajka
` Rob Hudson
` Janina Sajka
` Rob Hudson
` Janina Sajka
` Chris Brannon
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=C13A5884A1EC4BD2A0544819DDB8A44D@windows3f8340d \
--to=captinlogic@gmail.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).