From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup problems using vim 7.2
Date: Wed, 15 Apr 2009 21:16:43 +0200 [thread overview]
Message-ID: <20090415191643.GZ5326@const> (raw)
In-Reply-To: <20090415175136.GA6431@blackbird>
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Kitty Litter
` Zachary Kline
` Samuel Thibault [this message]
` Gaijin
` Janina Sajka
` Kitty Litter
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=20090415191643.GZ5326@const \
--to=samuel.thibault@ens-lyon.org \
--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).