public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
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: Speakup with vim
Date: Mon, 14 Feb 2011 16:18:50 -0500	[thread overview]
Message-ID: <A75329E15EF04F649051F00D1BEE5654@ownercb76d9f6c> (raw)
In-Reply-To: <4D598790.2040406@aim.com>

I liked the way Speakup worked with Emacs better than the way it works with
VIM.  I started out using Emacs.  I found the main drawback in Emacs for me
to be the multi-key combinations needed to do a lot of things:  it actually
was easier for me to adjust to Vim's different modes, although forgetting
which one you're in can punch your face good.  Also, I could not seem to
find in Emacs the means of saving word wrap and margin settings I wanted.  I
may be wrong, but my impression is that, like Emacspeak, Emacs itself has
quite the learning curve.

Just my wooden penny's worth.

Al 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Michael Whapples
Sent: Monday, February 14, 2011 2:51 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Speakup with vim

Thanks, that solves the specific issue. I still wonder if there is more
which can be done to make vim work better, eg. using j and k (I can imagine
they actually are quicker to use than cursor keys when you are used to them)
speakup doesn't speak the new line you navigate to unless the screen is
scrolling.

Is this as good as speech output gets with vim? Might it be worth me giving
emacs (may be with emacspeak) more time?

Michael Whapples
On -10/01/37 20:59, Samuel Thibault wrote:
> Michael Whapples, le Mon 14 Feb 2011 09:10:39 +0000, a écrit :
>> The one problem I notice most is that when I go into insert mode as I 
>> type speakup seems to read from the status line rather than the 
>> characters typed. Also related, when using j and k to move lines 
>> speakup reads the status line as well rather than the line being moved
to.
> See http://brl.thefreecat.org/wiki/vi to fix these.
>
> Samuel
>

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Michael Whapples
 ` Samuel Thibault
   ` Michael Whapples
     ` Albert Sten-Clanton [this message]
       ` Michael Whapples
         ` Bardia Zakeri
         ` Bardia Zakeri

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=A75329E15EF04F649051F00D1BEE5654@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).