edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Patrick Smyth <patricksmyth@fastmail.com>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: Cli-focused screen reader
Date: Fri, 9 Sep 2022 13:36:37 -0500	[thread overview]
Message-ID: <20220909183637.GA18584@mail.hallyn.com> (raw)
In-Reply-To: <87czc4wgl6.fsf@gmail.com>

On Fri, Sep 09, 2022 at 02:25:09PM -0400, Patrick Smyth wrote:
> Hi all,
> Apologies if this is a basic or trivial question, but I wanted to ask about
> setting up screen readers for the command line on Linux. I am using Linux
> Mint (functionally Ubuntu LTS), and while I can use Orca to read X11
> terminals, it's quite slow and annoying to use, and I'd prefer something
> specific to the terminal. I'm also pretty happy with speakup when I drop out
> of the graphical interface, so not looking for anything there.
> I've tried a couple command-line specific screen readers, and I've had a lot
> of trouble getting them to work. The two I've tried recently are tdsr
> (https://github.com/tspivey/tdsr) and fenrir
> (https://github.com/chrys87/fenrir). Setting aside Fenrir, since the setup
> is a lot more involved, when I run tdsr I get the following error
> ModuleNotFoundError: No module named 'speechd'
> I have speech dispatcher installed with aptitude (apt-get install
> speech-dispatcher). I downloaded the speech dispatcher project from GitHub
> and tried importing the Python API, but it gives me a circular import issue.
> Here's the speech dispatcher repo on GitHub, there's a clients folder with a
> Python library: https://github.com/brailcom/speechd
> If people have gotten speech dispatcher for Python or the tdsr screen reader
> working, I'd appreciate any guidance. If people are more familiar with
> fenrir, I can try to articulate where I'm stuck with that, but it's
> significantly more involved as a setup process. And apologies if edbrowse
> isn't the place for this kind of question, though it seems fairly likely
> some of us are using CLI screen readers in this community.
> Thanks, and hope you have a good end of the week!
> Best,
> Patrick

I'm sure there's much better things out there and I look forward to seeing
them listed here :)  But if I were to want this right now, I would write a
brief wrapper to wrap around a shell, which writes fd 1 and 2 output to
espeak.  (I've used espeak for several things like this, and love how easily
i can switch the voice and accent and speed and pitch.)  I'd be curious
however, for your use case, what you'd want to do about input.  Do you only
want output to be spoken, or do you want each character spoken, or the input
spoken when you hit return?  Also not sure whether you'd want stdout and
stderr interwoven, or whether that depends on whether the command has exited
or is interactive, etc.


  reply	other threads:[~2022-09-09 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 18:25 Patrick Smyth
2022-09-09 18:36 ` Serge E. Hallyn [this message]
2022-09-09 19:28   ` Adam Thompson
2022-09-09 19:38     ` Serge E. Hallyn
2022-09-09 19:18 ` Tyler Spivey
2022-09-09 22:22   ` Patrick Smyth
2022-09-14 19:31     ` Patrick Smyth

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220909183637.GA18584@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=patricksmyth@fastmail.com \


* 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).