* speakup problems using vim 7.2
@ Kitty Litter
` Zachary Kline
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Kitty Litter @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
I recently got a new machine and installed Debian Squeeze and the vim editor
along with latest speakup and 2.6.29.1 kernel. When I use vim in insert mode
speakup echoes 2 or 3 characters before the cursor. This even happens over
ssh connection so I suppose it really isn't a speakup problem. Anyone have a
clue how to configure vim so it doesn't do this?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: speakup problems using vim 7.2
speakup problems using vim 7.2 Kitty Litter
@ ` Zachary Kline
` Samuel Thibault
` Gaijin
` Janina Sajka
2 siblings, 1 reply; 6+ messages in thread
From: Zachary Kline @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Apr 15, 2009 at 01:41:42PM -0400, Kitty Litter wrote:
> I recently got a new machine and installed Debian Squeeze and the vim
> editor along with latest speakup and 2.6.29.1 kernel. When I use vim in
> insert mode speakup echoes 2 or 3 characters before the cursor. This even
> happens over ssh connection so I suppose it really isn't a speakup
> problem. Anyone have a clue how to configure vim so it doesn't do this?
I'm not quite sure what is happening here. I'm using vim to type this,
and noting no strange echoing. Any more specific information you can
give? (I'm not using Debian, but that shouldn't matter.
Best,
Zack.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAknmHqgACgkQ1dA/dtm5w2zcDwCeKEqGmEPtmYoN6dyczPN/S9V2
7WIAn3nToFT3jP1D8ftOxGqfrz+FOMrX
=gvJw
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: speakup problems using vim 7.2
` Zachary Kline
@ ` Samuel Thibault
0 siblings, 0 replies; 6+ messages in thread
From: Samuel Thibault @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Zachary Kline, le Wed 15 Apr 2009 10:51:36 -0700, a écrit :
> On Wed, Apr 15, 2009 at 01:41:42PM -0400, Kitty Litter wrote:
> > I recently got a new machine and installed Debian Squeeze and the vim
> > editor along with latest speakup and 2.6.29.1 kernel. When I use vim in
> > insert mode speakup echoes 2 or 3 characters before the cursor. This even
> > happens over ssh connection so I suppose it really isn't a speakup
> > problem. Anyone have a clue how to configure vim so it doesn't do this?
> I'm not quite sure what is happening here. I'm using vim to type this,
> and noting no strange echoing. Any more specific information you can
> give?
Check the .vimrc for instance.
Samuel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: speakup problems using vim 7.2
speakup problems using vim 7.2 Kitty Litter
` Zachary Kline
@ ` Gaijin
` Janina Sajka
2 siblings, 0 replies; 6+ messages in thread
From: Gaijin @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
On Wed, Apr 15, 2009 at 01:41:42PM -0400, Kitty Litter wrote:
> Anyone have a clue how to configure vim so it doesn't do this?
Are you in SpeakUP's "Highlight Tracking" mode. That has always
caused me problems in vim. If so, try the "Cursoring On" mode. HTH,
Michael
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: speakup problems using vim 7.2
speakup problems using vim 7.2 Kitty Litter
` Zachary Kline
` Gaijin
@ ` Janina Sajka
` Kitty Litter
2 siblings, 1 reply; 6+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Kitty Litter writes:
> I recently got a new machine and installed Debian Squeeze and the vim
> editor along with latest speakup and 2.6.29.1 kernel. When I use vim in
> insert mode speakup echoes 2 or 3 characters before the cursor. This even
> happens over ssh connection so I suppose it really isn't a speakup
> problem. Anyone have a clue how to configure vim so it doesn't do this?
Well, it's not you and it's not Debian. I'm seeing the same under
Fedora. I believe this problem arrived with vim 7. I am now on Fedora
7.2 and this problem is definitely there. I don't know what is causing
it or how to cure it. It is very annoying, needless to say.
I can describe it a bit more precisely, I think.
* The first char typed on a line will echo just that char.
* The second, and every subsequent, char will attempt to pronounce
* the two chars or read them out separately. For instance, if the
* first char is an 'a', Speakup will say a. If the second char is
* a 'd', Speakup will say 'ad'. If the first is a 'b' and the
* second a 'd', Speakup says 'bd'.
Janina
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
Janina Sajka, Phone: +1.202.595.7777;
sip:janina@CapitalAccessibility.Com
Partner, Capital Accessibility LLC http://CapitalAccessibility.Com
Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com
Chair, Open Accessibility janina@a11y.org
Linux Foundation http://a11y.org
Chair, Protocols & Formats
Web Accessibility Initiative http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: speakup problems using vim 7.2
` Janina Sajka
@ ` Kitty Litter
0 siblings, 0 replies; 6+ messages in thread
From: Kitty Litter @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
This problem went away after several upgrades where I seem to have a
different locale. Problem also fixed if you set LANG=C
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
speakup problems using vim 7.2 Kitty Litter
` Zachary Kline
` Samuel Thibault
` Gaijin
` Janina Sajka
` Kitty Litter
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).