linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Chris Brannon <chris@the-brannons.com>,
	deedra@the-brannons.com, Okash Khawaja <okash.khawaja@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	speakup@linux-speakup.org, devel@driverdev.osuosl.org,
	William Hubbs <w.d.hubbs@gmail.com>,
	Kirk Reiser <kirk@reisers.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Staging status of speakup
Date: Sat, 16 Mar 2019 11:22:02 +0100	[thread overview]
Message-ID: <20190316102202.py3qczl3g4fw3myn@function> (raw)
In-Reply-To: <20190316093543.w4i6djt5uuqtx5xr@function>

Hello,

Please keep the lists in Cc, so that not only I have the information
(in particular since I will probably *not* have the time to investigate
myself).

Samuel Thibault, le sam. 16 mars 2019 10:35:43 +0100, a ecrit:
> The problem is that neither Okash nor I are even casual users of
> speakup, so we need a walk-through of the kind of operation that
> produces the issue.

deedra Waters <deedra@the-brannons.com> wrote:
> it's dead simple

For a user, perhaps, but again, neither Okash or I are actual users of
speakup, so we have just no idea what casual use is.

> just lead the screenreader read large blocks of text i guarantee it's
> reproduceable.

Which shortcut do you use to make the screen reader read it?  What is
"large"? Is that only one 80x25 complete output screen? Is that cat-ing
a long text? How is it garbled: is that right from the beginning of the
text? or at some point during it? or is that just a piece of it and then
it's Ok again?

Samuel

  reply	other threads:[~2019-03-16 10:22 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 13:01 Staging status of speakup Okash Khawaja
2019-03-16  1:19 ` Chris Brannon
2019-03-16  9:35   ` Samuel Thibault
2019-03-16 10:22     ` Samuel Thibault [this message]
2019-03-19 16:31     ` Alan Cox
2019-03-19 17:07       ` Samuel Thibault
2019-03-19 17:11       ` Adam Borowski
2019-03-20 20:54       ` Okash Khawaja
2019-03-16 10:05   ` Okash Khawaja
2019-03-16  3:18 ` Greg Kroah-Hartman
2019-03-16 10:09   ` Okash Khawaja
2019-07-06 19:08   ` Okash Khawaja
2019-07-07  6:57     ` Greg Kroah-Hartman
2019-07-12  8:38       ` Greg Kroah-Hartman
2019-07-12  9:23         ` [HELP REQUESTED from the community] Was: " Samuel Thibault
2019-07-13  0:46           ` Gregory Nowak
2019-07-25  3:53             ` Gregory Nowak
2019-07-25  4:04               ` Chris Brannon
2019-07-25 10:44                 ` John Covici
2019-08-21 16:39                   ` Okash Khawaja
2019-08-21 22:22                     ` Gregory Nowak
2019-09-08  9:43                       ` Okash Khawaja
2019-09-09  2:54                         ` Gregory Nowak
2019-09-14 21:08                           ` Okash Khawaja
2019-09-14 23:32                             ` Samuel Thibault
2019-09-15 13:43                             ` Greg Kroah-Hartman
2019-09-15 18:41                               ` Okash Khawaja
2019-09-16 13:47                                 ` Samuel Thibault
2019-09-16 14:11                                   ` Greg Kroah-Hartman
2019-09-16 22:38                                     ` Gregory Nowak
2019-09-17  8:01                                       ` Greg Kroah-Hartman
2019-09-18  1:03                                         ` Gregory Nowak
2019-09-18  6:16                                           ` Greg Kroah-Hartman
2019-09-18 20:30                                             ` Gregory Nowak
2019-09-20  7:46                                               ` Greg Kroah-Hartman
2019-09-20 10:18                                                 ` Okash Khawaja
2019-09-16 20:21                                   ` Gregory Nowak
2019-07-25  6:11               ` Willem van der Walt
2019-07-25  6:33                 ` Greg Kroah-Hartman
2019-07-25 10:41               ` John Covici
2019-07-12  9:24         ` Okash Khawaja

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=20190316102202.py3qczl3g4fw3myn@function \
    --to=samuel.thibault@ens-lyon.org \
    --cc=chris@the-brannons.com \
    --cc=deedra@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okash.khawaja@gmail.com \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@gmail.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 NNTP newsgroup(s).