Re: [orca-list] gvim

["B. Henry" <burt1iband gmail com>]

Gedit has some very nice plug-ins also, but I do use CLI editors a lot, especially as I do as much as is 
practical in CLI 
invironments. I have usedVIM some, ed more, and have nano as my default txt editor. I run all but nano 
exclusively in CLI 
ttys. Nano I sometimes run in terminal emulators which works fine as long as the terminal is meximized. The 
only issues I 
have are the slight delay switching back to the GUI from a shell or other cli program that would not be 
noticeable on a 
fast machine I think, and the extra time spent with copy and paste operations between CLI and GUI. I keep a 
couple files 
around for this, pasting with speakups "cut and paste" functionality and then using GUI copy and paste 
shortcut keys to 
move the text around in the desktop invironment or visa versa. I have a script that works with a clipboard 
manager that 
can avoid much of this hassle, but I have never started using it. 
--
B.H.
 

On Thu, May 29, 2014 at 08:26:55AM +0200, Vojtěch Polášek wrote:
> Hi,
> well I vanted to use Vim from the command line, but orca behaves veirdly
> with it.
> Maybe it can be fixed.
> I open Vim from Gnome terminal and press A to append text.
> I can write fine.
> But when I try to read text by pressing up and down arrows, it behaves
> inconsistently. sometimes it reads a line without problems, sometimes it
> reads just "Empty", sometimes it reads "empty" and the line...
> How do you use it?
> Were you able to get Emacs to work? I like gedit, so far, but I would
> like to use some of those editors because there are loads of nice
> plugins for them.
> Thanks,
> Vojta
>
>
> Dne 29.5.2014 04:04, Alex Midence napsal(a):
> > Plain old Vim works well.  Just access it as a CLi application and not a GUI one.  Iv you don't like Vim, 
> > you can use another VI port like Elvis or something.  Eitehr way, it's very useful to learn as it is 
> > ubiquitous.
> >
> > Alex M
> >
> >
> > -----Original Message-----
> > From: B. Henry [mailto:burt1iband gmail com] 
> > Sent: Wednesday, May 28, 2014 5:40 PM
> > To: Alex Midence; orca-list gnome org
> > Subject: Re: [orca-list] gvim
> >
> > I think aviword draws the text using some kind of bitmap as it were instead of using normal text, or at 
> > least that is what I was told a few years ago. I have no idea about gvim, but have not heard of it being 
> > accessible. I have always stuck with using traditionally cli editors in VTs, and gedit, mouse-pad or 
> > bluefish when working in a graphical invironment, although I must confess I've started nano by reflex 
> > quite a few times when in a terminal emulator.
> > --
> > B.H.
> >
> > On Wed, May 28, 2014 at 04:10:16PM -0500, Alex Midence wrote:
> > > I have never been able to use Gvim with gtk interface.  The menus are 
> > > accessible but the widget containing the text you are typing is not.  
> > > I do not know why.  Similar behavior can be observed in applications 
> > > like Abiword and Gnumeric.
> > >
> > > alex M
> > >
> > >
> > > -----Original Message-----
> > > From: orca-list [mailto:orca-list-bounces gnome org] On Behalf Of 
> > > Vojtech Polášek
> > > Sent: Wednesday, May 28, 2014 3:57 PM
> > > To: orca-list
> > > Subject: [orca-list] gvim
> > >
> > > Hi,
> > > I wanted to start with Vim, however if I want to use it in Gnome 
> > > terminal, it is not very pleasant, because Orca is reading "empty line"
> > > before every line.
> > > I tried to install Gvim - Vim with GTK interface, but this doesn't 
> > > read lines at all.
> > > Can I help you somehow to debug this? It should use normal GTK 
> > > interface so I don't know, why there exists a problem.
> > > Thanks,
> > > Vojta
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > Visit http://live.gnome.org/Orca for more information on Orca.
> > > The manual is at
> > > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > > Log bugs and feature requests at http://bugzilla.gnome.org Find out 
> > > how to help at http://live.gnome.org/Orca/HowCanIHelp
> > >
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > Visit http://live.gnome.org/Orca for more information on Orca.
> > > The manual is at 
> > > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > > Log bugs and feature requests at http://bugzilla.gnome.org Find out 
> > > how to help at http://live.gnome.org/Orca/HowCanIHelp
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Visit http://live.gnome.org/Orca for more information on Orca.
> > The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Log bugs and feature requests at http://bugzilla.gnome.org
> > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp