[BlindRUG] Windows 11 and the R terminal
Jonathan Godfrey
A.J.Godfrey at massey.ac.nz
Wed Aug 28 21:05:27 UTC 2024
Hello all,
A recent Windows update caused me and my use of the R terminal quite some grief. I should note that the grief was greater with JAWS than NVDA, and updating JAWS to the latest version (2024...) did not help.
Windows 11 now uses a smarter terminal for all apps wanting to use a terminal, replacing the power shell and the older command prompt with a more modern look and feel terminal. The new one has tabs and other things which I do not want.
This affected my use of the R terminal, batch files, Python, and of course the DOS command prompt which I use much more frequently than the standard Windows user. It also affects the context sensitive menu (Shift+f10), now offering to open blah in a terminal; gone are direct references to command prompt or the power shell.
With some sighted IT help, and a conversation with a blind person of an older generation, I found the right settings in the new terminal to minimise its use and therefore impact. Furthermore, I have found a way to know if the "look" is old or new.
First, the check: Attempt to open a command prompt from the run menu (Windows+R, and typing cmd). This used to open a command prompt showing the current folder. The problem is that the new terminal might sound the same even if it looks different. If you are using the new version, a settings option is available as the bottom item on the Alt+Space menu. If you can't get to settings, you're in the old school command prompt.
To fix: If you have the setting item, make use of it. Note that JAWS did not read the changes I was making in this dialogue so there was a lot of tabbing and back-tabbing required to be sure I got what I wanted. The dialogue should be offering to make changes to the startup settings (first of six choices). This is what we want so tab across a few times, just past the "startup" button. There are two drop down lists that we must check. The first lists different terminals, starting with power shell, command prompt, etc. To check my selection, I had to tab and back-tab here. The next one is the more important one where it is probably set to letting windows decide. The second option mentions the word "console", while the third mentions "terminal". Choose the console. Further on, make sure the settings open a new window (as against multiple tabs), and make sure you tab over to and select "save". You do not have a "close" button here so Alt+f4 to get out.
Repeat the check step. The settings item will have disappeared if the changes took effect.
These changes do not affect the options in Windows Explorer, so you will be able to get back to the new terminal later. This does mean though that the use of a shortcut to run the command prompt in a specific folder has increased in importance to me. My shortcut points explicitly to C:\windows\system32\cmd.exe
I would also observe that as well as the R terminal working as it used to do, my command line experience is restored to a level which allowed me to tinker with some Python tools this week.
I hope this helps anyone who may suffer a Windows upgrade soon.
All the best,
Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/blindrug_nfbnet.org/attachments/20240828/f4af5ae4/attachment.htm>
More information about the BlindRUG
mailing list