From: William Hubbs <williamh@gentoo.org>
To: gentoo Accessibility <gentoo-accessibility@lists.gentoo.org>
Subject: Re: Ufed accessibility]
Date: Sat, 1 May 2004 14:01:16 -0500 [thread overview]
Message-ID: <20040501190116.GA10449@linux1.home> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- ----- Forwarded message from William Hubbs <williamh@gentoo.org> -----
Date: Fri, 30 Apr 2004 19:52:25 -0500
From: William Hubbs <williamh@gentoo.org>
To: gentoo-accessibility@lists.gentoo.org
Subject: Re: [gentoo-accessibility] Ufed accessibility
Hi all.
I think what is happening here is similar to the way pine behaves if the show cursor option is turned off.
A bug has been filed against ufed requesting a "show cursor" option or requesting that ufed be changed to show the cursor by default.
http://bugs.gentoo.org/show_bug.cgi?id=49555
Feel free to add your comments to this bug if you have more information.
Thanks,
William
On Fri, Apr 30, 2004 at 07:55:51PM +0100, Toby Fisher wrote:
> Quick background for those who don't know, Ufed is a package that gives a
> curses interface to all the use flags, relly useful imho.
>
> There's only 1 problem though imho. For some reason, using Speakup with
> this package is more difficult than it might be because cursor tracking
> doesn't work, reading the current line always shows the save/help/exit
> line, not the line of the currentl,y highlighted flag.
>
> Does anyone know either if there's something else I need to do or whether
> this might be fixed in the future?
>
> Thanks.
>
>
> --
> Toby Fisher Email: toby@tjfisher.co.uk
> Tel.: +44(0)1480 417272 Mobile: +44(0)7974 363239
> ICQ: #61744808
>
> --
> gentoo-accessibility@gentoo.org mailing list
>
- ----- End forwarded message -----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAk/P8blQW9DDEZTgRAoQMAJ9P0bhW+TswpnY5EhUWmcQWob1ergCgkaMg
xbXSTYIntunQjIB/CjUYpMM=
=Pl1J
-----END PGP SIGNATURE-----
reply other threads:[~2004-05-01 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040501190116.GA10449@linux1.home \
--to=williamh@gentoo.org \
--cc=gentoo-accessibility@lists.gentoo.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