From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: If bash can, why not Speakup?
Date: Wed, 17 Nov 2010 17:30:43 -0600 [thread overview]
Message-ID: <20101117233043.GA26689@linux1> (raw)
In-Reply-To: <98haom$7bpkcl@ipmail06.adl6.internode.on.net>
On Thu, Nov 18, 2010 at 09:23:29AM +1000, pj@pjb.com.au wrote:
> Janina Sajka wrote:
> > I've been happily using vim for years.
>
> How do you cope with the endlessly-updating bottom line?, like:
> "497L, 15593C 450,2 93%"
>
> I find speakup is in general difficult with curses applications
> because of their screen-update optimisation. The characters
> don't necessarily come out in a text-related order.
You can disable that line by putting the following line in your
~/.vimrc:
set noruler
> > My biggest complaint is that I need to be ultra-careful to
> > track whether I'm in insert or command mode, i.e. it would
> > sure help if Speakup could give me a differently pitched voice
>
> Good point :-) It might need some help from the vim folk...
Yes, something like this would take modifications to vim to make it
communicate to speakup some how, and I'm not sure what that would
involve since I haven't looked at the vim code at all.
William
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
pj
` William Hubbs [this message]
` Albert Sten-Clanton
` Steve Holmes
` Gregory Nowak
` Steve Holmes
` Gregory Nowak
` Janina Sajka
` Speech on vim backspace [Was: If bash can, why not Speakup?] Janina Sajka
` Albert Sten-Clanton
` If bash can, why not Speakup? Janina Sajka
` Rynhardt Kruger
` William Hubbs
-- strict thread matches above, loose matches on Subject: below --
pj
` William Hubbs
` Janina Sajka
Brian Buhrow
pj
pj
Janina Sajka
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=20101117233043.GA26689@linux1 \
--to=w.d.hubbs@gmail.com \
--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).