From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup and dialog
Date: Fri, 13 Nov 2009 11:17:29 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.0911131115240.2719@localhost.localdomain> (raw)
In-Reply-To: <95d95eac-29db-43ae-ad64-9d1c891c416d@default>
You might be able to use dialog with highlight tracking enabled in
speakup.
I use lots of ncurses packages with speakup without problems, but in most
cases, with some configuration changes to the package.
On Thu, 12 Nov 2009, Donald Raikes wrote:
> Hello,
>
>
>
> I am wondering if it is possible to use the dialog package with speakup.
>
> I want to create several shell scripts that present information and ask for choices/input via the dialog package, however, I have discovered that speakup doesn't seem to work very well with ncurses packages in general like dialog.
>
>
>
> Any tips on how to configure either dialog or speakup to make them work well together would be appreciated.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Donald Raikes
` Willem van der Walt [this message]
` Kirk Reiser
` Chris Brannon
` Steve Holmes
` Garrett Klein
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.0911131115240.2719@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--cc=speakup@braille.uwo.ca \
/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).