From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: old artic transport, some ideas.
Date: Tue, 30 May 2017 18:04:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1705301804330.25296@server2.shellworld.net> (raw)
In-Reply-To: <99916d4a-c861-072e-9133-8fbabb29da18@crosslink.net>
Its in the manual I suspect.
On Thu, 25 May 2017, Linux for blind general discussion wrote:
> I think the command set was a control-e followed by a character v for volume,
> r for rate, p for pitch. Then you had nine levels
>
> sample: control-er9 set the fastest rate.
>
> Could be wrong.
>
>
>
>
> On 5/25/2017 10:26 PM, Linux for blind general discussion wrote:
>> On Fri, May 26, 2017 at 12:16:09PM AEST, Linux for blind general
>> discussion wrote:
>> > Hi Mark,
>> > Santa has come early if you have an interest.
>> > I have for you a copy of the documentation for the artic transport.
>> Does that documentation happen to also contain the command set to talk to
>> the
>> transport hardware?
>>
>> Luke
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
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=Pine.LNX.4.64.1705301804330.25296@server2.shellworld.net \
--to=blinux-list@redhat.com \
/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).