From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: suggestions for Speakup
Date: Sat, 12 Jan 2002 01:22:49 -0500 [thread overview]
Message-ID: <002601c19b31$8f474540$0100a8c0@tward> (raw)
In-Reply-To: <Pine.LNX.4.43.0201121351020.462-100000@data.home>
Hi, I never heard about that method before. I'll have to try it.
----- Original Message -----
From: Geoff Shang <gshang@uq.net.au>
To: <speakup@braille.uwo.ca>
Sent: Friday, January 11, 2002 11:08 PM
Subject: Re: suggestions for Speakup
> On Fri, 11 Jan 2002, Thomas Ward wrote:
>
> > For example while in pine it reads the prier email subject and then the
> > current one. I'd much rather see that quark be fixed rather than search
> > features, exception dictionaries, etc.
>
> I assume this is when you arrow or use n and p to move through the index,
> but you didn't say so I'm having to guess here. This is because pine is
> defaulted to show the selected message in a different type to all the
> others, and thus it has to rewrite the prior entry before highlighting the
> new one. This is a common problem in many applications.
>
> As an aside, I have "assume slow link" on which doesn't use such
> highlighting, it just uses a greaterthan symbol to point out the current
> message. Although, if you're relying on prev and next to give you the
> subject, this won't help you as it doesn't have to reprint the subject
> anymore. This doesn't personally bother me as I use speakup's reviewkeys
> to read the index and just enter the message number of the message I want
> (made easier with enable jump shortcut).
>
> Geoff.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` Gregory Nowak
` Saving Settings--Was " Dave Hunt
` More Speakup Suggestions--was " Dave Hunt
` Geoff Shang
` What is the search feature??? Dave Hunt
` Geoff Shang
` suggestions for Speakup Thomas Ward
` Kirk Reiser
` Charles Hallenbeck
` Shaun Oliver
` Amanda Lee
` Raul A. Gallegos
` Kirk Wood
` Janina Sajka
` speakup howto, was: " Gregory Nowak
` Janina Sajka
` Gregory Nowak
` Janina Sajka
` Gregory Nowak
` Saqib Shaikh
` Janina Sajka
` Saqib Shaikh
` Janina Sajka
` Geoff Shang
` Thomas Ward
` Saqib Shaikh
` Saqib Shaikh
` Janina Sajka
` Steve Holmes
` Gregory Nowak
[not found] ` <Pine.LNX.4.33.0201110959570.1483-100000@hudson.mhonline.ne t>
` Jason Symes
` Kirk Reiser
` Gregory Nowak
` Steve Holmes
` Raul A. Gallegos
` Geoff Shang
` Raul A. Gallegos
` Thomas Ward
` Geoff Shang
` Thomas Ward [this message]
` Kirk Wood
` Thomas Ward
` Janina Sajka
` Kirk Wood
` Steve Holmes
` Thomas Ward
` Gregory Nowak
` Kirk Wood
` Gregory Nowak
` Kirk Wood
` Thomas Stivers
` Gregory Nowak
` Thomas Ward
` Kirk Wood
` Thomas Ward
` Geoff Shang
` Janina Sajka
` Gregory Nowak
` Amanda Lee
` Kirk Wood
` Geoff Shang
[not found] <E16P3vX-0002KB-00@speech.braille.uwo.ca>
` Adam Myrow
` Geoff Shang
` Charles Hallenbeck
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='002601c19b31$8f474540$0100a8c0@tward' \
--to=tward@bright.net \
--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).