Hi,
Have you tried Vi on Windows Subsystem for Linux (WSL)?
This is then a console experience. I notice NVDA still reads all the cursor
positions as they update in the status bar.
JAWS does this cursor location echoing too but I can set JAWS screen echo to
None (JAWSKey+s) and stop this announcement and then Vi works fairly well
including tracking the cursor.
I cannot find that NVDA has a similar feature but perhaps someone else knows?
Otherwise though I agree VSCode is a good choice and on Windows long-term you
may find a more beneficial experience. When it comes to Python VSCode also
supports Jupyter Notebooks right in its interface which is a nice feature.
-Travis
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Florian Beijers
Sent: Monday, January 24, 2022 1:58 PM
To: program-l <program-l@xxxxxxxxxxxxx>
Subject: [program-l] Re: New member
Hi Mani,
What was stated is essentially that Vim does not work with NVDA or indeed even
Orca, and that VS Code is your best bet. Thing with VS Code is that it does
require you to be pretty proficient with your screen reader.
I made a bit of an audio walkthrough of the program back in 2020, some of it
may have changed slightly, but it might be useful :)
https://www.dropbox.com/s/ypax4q266v1ur2h/VS%20Code%20Walkthrough.mp3?dl=0
Op ma 24 jan. 2022 om 19:46 schreef Mani Iyer <dmarc-noreply@xxxxxxxxxxxxx
<mailto:dmarc-noreply@xxxxxxxxxxxxx> >:
Hello Florian and Soundarya,,
For some reason I did not get Soundarya’s email message in my inbox. I checked
the Spam folder and it wasn’t there.
Anyway, I have never used emacs and I believe it has a long learning curve. And
do I have to use emacspeak with it? I did download VS Code for community and
felt it too daunting. Is there a ‘Beginner’s Guide’ or ‘Getting Started’
tutorial on VS Code that I can quickly go over?
Any information on accessibility settings will be welcome too.
Warmly,
Mani G. Iyer
On Jan 24, 2022, at 12:58 PM, Florian Beijers <florianbeijers@xxxxxxxxx
<mailto:florianbeijers@xxxxxxxxx> > wrote:
Soundarya,
Do you have experience with emacspeak within the wsl2 vm? How's audio
latency/crackle?
Thanks,
FLorian
2022-01-24 18:02 GMT+01:00, Soundarya Pradhan <soun.chess@xxxxxxxxx
<mailto:soun.chess@xxxxxxxxx> >:
Hello,** To leave the list, click on the immediately-following link:-
Welcome to the group.
Vim does not work with nvda, in fact even it does not work with orca to a
reasonable extent as far as my experienced with linux is concerned.
If VS code is suffitient for your current use case, I would recommend it.
It works really well with nvda.
Also if you have tried emacs then there is a wonderful way to get it
accessible, with the help of emacspeak.
WSL2 can help in using it on windows.
Regards,
Soundarya
On Mon, Jan 24, 2022 at 10:12 PM Mani Iyer <dmarc-noreply@xxxxxxxxxxxxx
<mailto:dmarc-noreply@xxxxxxxxxxxxx> >
wrote:
Hello all,
I am sorry for not introducing myself prior to posting some emails to the
list.
I am a retired software developer trying to get back to programming after
11 years for the fun of it. After being a Mac user for more than a decade
I
decided to learn NVDA on Windows and slowly get myself back into
programming Python. I used vim when I was sighted years ago and wanted to
go back to it. I quickly landed into issues:
1) NVDA speaks some number along with every character I
I type. I thought it was the column number but it does not seem so.
2) After insert mode I type Esc to issue some : commands and it does not
seem to work. I end up having to kill vim to get out of it.
My questions are :
1) Does vim work well with NVDA? If so, are there some pre requisites to
follow like configuration changes?
2) Should I just forget vim and resort to a more NVDA-friendly Python
editor? And which may they be. I was thinking of EdSharp but look to
other
suggestions from you.
Sorry for the long post. Thank you.
Mani
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx ;
<mailto:program-l-request@xxxxxxxxxxxxx> ?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx <mailto:program-l-request@xxxxxxxxxxxxx>
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx ;
<mailto:program-l-request@xxxxxxxxxxxxx> ?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx <mailto:program-l-request@xxxxxxxxxxxxx>
with the Subject:- faq
** [mailto:program-l-request@xxxxxxxxxxxxx ;
<mailto:program-l-request@xxxxxxxxxxxxx> ?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx <mailto:program-l-request@xxxxxxxxxxxxx>
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx ;
<mailto:program-l-request@xxxxxxxxxxxxx> ?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx <mailto:program-l-request@xxxxxxxxxxxxx>
with the Subject:- faq
