From: "Albert Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Speech on vim backspace [Was: If bash can, why not Speakup?]
Date: Thu, 18 Nov 2010 18:50:11 -0500 [thread overview]
Message-ID: <52000CE9605B4F2786079C7CB90EEF97@ownercb76d9f6c> (raw)
In-Reply-To: <20101118203131.GE2358@sonata.rednote.net>
Thanks, Janina.
Al
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Janina Sajka
Sent: Thursday, November 18, 2010 3:32 PM
To: Speakup is a screen review system for Linux.
Subject: Speech on vim backspace [Was: If bash can, why not Speakup?]
Albert Sten-Clanton writes:
> In addition to the suggestion below, I'd very much like to hear the
> characters I'm backspacing over. I asked about this a few years ago,
> but I gathered that this wasn't easy to do. Any thoughts?
I have speech on backspace in vim, at least I do in insert mode.
You may need to set your charset to iso 8859-1 in your .vimrc. I don't
recall specifically whether this problem is solved, but other nasties are
solved this way. I'd love to use utf, but it isn't speaking as cleanly as
8859-1.
Janina
_______________________________________________
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: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
If bash can, why not Speakup? pj
` William Hubbs
` 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 [this message]
` If bash can, why not Speakup? Janina Sajka
` Rynhardt Kruger
` William Hubbs
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=52000CE9605B4F2786079C7CB90EEF97@ownercb76d9f6c \
--to=albert.e.sten_clanton@verizon.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).