From: Rynhardt Kruger <rynkruger@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: If bash can, why not Speakup?
Date: Thu, 18 Nov 2010 22:50:49 +0200 [thread overview]
Message-ID: <20101118205049.GA9342@blind-archer> (raw)
In-Reply-To: <20101118202718.GD2358@sonata.rednote.net>
I may be wrong, but I think that the vim editing style of bash isn't really the vim editor, but just a vim-like mode
provided by readline. For instance, pressing the colon (:) while in bash vim-style command-mode, doesn't allow you to
enter a vim command, but just beeps at you. So I think it's probably just a boolean value in the readline library itself
which indicates to the shell whether you are in insert or command mode.
Take care,
Rynhardt
* Janina Sajka <janina@rednote.net> [101118 22:31]:
> I think my main point got lost in the litany of vim complaints that have
> actually been with us for a long time. I was trying to say something new
> that no one has commented on. So, let me try to redirect, if I may ...
>
> William Hubbs writes:
> > On Thu, Nov 18, 2010 at 09:23:29AM +1000, pj@pjb.com.au wrote:
> > > Janina Sajka wrote:
> > > > 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.
> >
> Actually, I don't think we need anything from vim.
>
>
> Note that you can have either vim or emacs editing of bash commands.
> Emacs is the default, but you can reset this by issuing:
>
> set -o vim
>
> By, default, this provides bash shell command editing in insert mode. As
> in vim, pressing Esc takes you into command mode where all the vim
> command mode functionality is provided.
>
> So, the shell knows. That's got to be a value that's written somewhere,
> and thus something Speakup could read and respond to. I don't know
> where, but am I wrong?
>
> Janina
>
> > William
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
>
> Janina Sajka, Phone: +1.443.300.2200
> sip:janina@asterisk.rednote.net
>
> 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)
>
> _______________________________________________
> 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: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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
` If bash can, why not Speakup? Janina Sajka
` Rynhardt Kruger [this message]
` 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=20101118205049.GA9342@blind-archer \
--to=rynkruger@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).