From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: John Covici <covici@ccs.covici.com>
Cc: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: speakup paste problem on debian
Date: Sun, 8 Nov 2020 19:10:14 +0100 [thread overview]
Message-ID: <20201108181014.2bcg4ryy4hzjcgng@function> (raw)
In-Reply-To: <m3361kpcmb.wl-covici@ccs.covici.com>
John Covici, le dim. 08 nov. 2020 01:49:00 -0500, a ecrit:
> But speakup-r reads a document, as long as it has a
> cursor, by sending down arrows and keeping track of what speech was
> actually sent by means of the synthesizers index marks. Then when you
> stop the reading, the cursor is where you stopped.
Ah, that's read_all_doc then. Ok, I'll add it to the spkguide so at
least people know about it.
Is that working with software speech?
Samuel
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Hart Larry
` Rob Hudson
` Gregory Nowak
` Jason White
` Janina Sajka
` Deedra Waters
` Jason White
` covici
` Samuel Thibault
` John Covici
` Samuel Thibault [this message]
` John Covici
` Samuel Thibault
` Alexander Epaneshnikov
` Samuel Thibault
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=20201108181014.2bcg4ryy4hzjcgng@function \
--to=samuel.thibault@ens-lyon.org \
--cc=covici@ccs.covici.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).