ins and keypad enter

[Gregory Nowak]

Bare in mind that lynx and pine and most of that other stuff doesn't use xdialoge.  Pine and lynx will have to wait until the cursoring problem gets fully solved.  As for now, lynx is not all that hard to navigate in.
Greg



> ----- Original Message -----
>From: Deedra Waters <dmwaters at tampabay.rr.com
>To: speakup at braille.uwo.ca
>Date: Sun, 16 Sep 2001 16:02:10 -0400 (EDT)
>Subject: ins and keypad enter

>     Ok, now I'm a little confused...I use lynx for a web browser which
>tracks a little strange but it's livable.  basically it speaks the line
>before and the current like when I use the arrows to move up and down to
>read the screen...  pine also does the same thing when I move threw
>messages which is a little confusing at first but I've learned to just
>sorta deal with it...

>     When I was using the make menuconfig option to recompile my kernel
>yesterday I had the same problem accept that when I'd read current line
>it'd not read the current line at all and would just say blank or
>something to that effect.

>     Kerk said that if I turned off the speech using ins keypad enter it'd
>track a lot better...  I'm confused now, because if I do that and then use
>the arrow keys to move around in say for example lynx, it doesn't talk at
>all when I move...  I want to know what the difference is then? If I go to
>recompile the kernel tomorrow and I use the arrow keys and it doesn't talk
>when I move up and down ect, how is this going to work?


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