Re: [orca-list] Vim, is it usable for us?

[Janina Sajka <janina rednote net>]

Orca screen reader developers writes:
> ...
> ... It's being said, that once one truly masters Vim, that
> person will consider any graphical editor very slow. That's of course for
> sighted people, I don't know, whether that's also true for blind folks.

I would agree with that remark. I've been using vim since it just called
vi.

Sorry I can't help with fenrir, but something is definitely amiss there.
But, glad to hear you got things working for vim and Orca. That's
awesome. Please keep us aprised.

Best,

Janina

> Gonna check it out. :P
>
>
> Best regards
>
>
> Rastislav
>
>
> Dňa 31. 8. 2020 o 23:20 Mewtamer napísal(a):
> > Okay, most linux systems have a number of consoles, usually named tty1-tty12.
> >
> > The GUI usually runs on tty1 and switching to tty2, tty3, etc. will
> > usually give you a text-based login prompt followed by the Linux
> > console.
> >
> > On most GUIs, ctrl+alt+a function key will switch to the tty whose
> > number corresponds to the function key used(e.g. ctrl+alt+f2 will
> > switch you to tty2) and when in a console not running a GUI, alt+a
> > function key will do the same.
> >
> > Some systems will have higher ttys(e.g. tty13-tty24), but I'm not sure
> > how these are accessed when present.
> >
> > The general idea for using both graphical and text screen readers in
> > combination is that You'd have the GUI running in tty1 and would use
> > Orca with GUI applications in tty1. Meanwhile, the text screen reader
> > would be running on tty2-tty12 and you would switch to those consoles
> > for using command line and other text-mode applications with the text
> > screen reader.
> >
> > If sound is properly configured, than you should be able to seemlessly
> > switch back and forth between graphical and text modes by switching
> > between ttys with the appropriate screen reader reading what you need
> > it to read on the active tty. And even without the switching between
> > graphical nd text modes, switching ttys is a powerful tool for
> > multi-tasking at the command line.
> >
> > For example, if I'm writing something, I might have Firefox and Orca
> > running on tty1 incase I need to look something up online, my work
> > document open in an editor in tty2, tty3 in the same working directory
> > as tty2 to use wc to keep track of word count on my work document
> > without having to close or suspend the editor, I might use tty4 to
> > pull up local files from elsewhere on my machine, and I might have
> > some time consuming, automated process running in the background on
> > tty5.
> >
> > Orca can work with terminal emulators, but I generally find switching
> > to a tty that isn't running a GUI and using a text screen reader is
> > often more straight forward for most text-only applications.
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa