[BlindRUG] Trouble accessing output

Fri Sep 15 14:42:22 UTC 2023

Thank you for these useful settings, JooYoung, and for  your continuing work to improve the accessibility of VSCode.
As it stands, it seems that the cursor is placed at the start of the code that is sent to the terminal. My preference would usually be for the cursor to be placed at the bottom, from where I would scroll up. This is because I typically send a block of code to R, and I would then like to immediately inspect the output. Of course I can just press ctrl+end to jump to the end of the accessible buffer, it’s just one extra keystroke.
My main issue with working with R in VSCode at present are the difficulties in working directly at the console. In Emacs, I can easily move back through my command history, edit a previous command and execute the modified command. As far as I can tell, at the moment one can not easily edit previous commands in the terminal, you can switch to the accessible buffer which shows the code on the current line, but that’s quite cumbersome and you don’t have any feedback when deleting characters in the terminal window, for example. My understanding is that a lot of the accessibility work has (understandably) been directed towards more standard terminal interfaces, such as Windows Power Shell and the standard Windows command line. If you have any advice regarding interacting with R at the console, I would be very glad to hear it.

In general I am excited about using R in VSCode, and I hope to move to this IDE permanently in the future.

All the best,
Robin

From: BlindRUG <blindrug-bounces at nfbnet.org> On Behalf Of Seo, JooYoung via BlindRUG
Sent: Friday, September 15, 2023 1:24 AM
To: Blind R Users Group <blindrug at nfbnet.org>
Cc: Seo, JooYoung <jseo1005 at illinois.edu>
Subject: Re: [BlindRUG] Trouble accessing output

Hello Miso,

This is because the VSCode has recently changed the keybinding for the terminal area and the shift+tab will no longer work. FYI, the ctrl+K, and ctrl+` is the custom keybinding that I added to the accessible DS profile for our summer workshop and that is not an universal key stroke. Instead, you can use the universal keystroke, alt+F2 in terminal input area to open an accessible terminal output buffer. However, this might be inconvenient, thus I suggest the following settings.

find the following settings and adjust it them as follows. FYI, you can adjust the setting value by pressing enter key on each setting name. You can then change value by pressing UpArrow and DownArrow. Once you choose each desired setting value, press enter to select and press ctrl+W key to close the setting window.

* Setting name: terminal.integrated.focusAfterRun
* Value: accessible-buffer

* Setting name: terminal.integrated.defaultLocation
* Setting value: view

* Setting name: r.source.focus
* Setting value: none

After this configuration, you can execute your R code in source editor by pressing ctrl+enter and your focus will be automatically moved to the executed terminal output buffer area.

To go back to your source editor, press ctrl+1.

Hope this helps.

All the best,

JooYoung

--------------------
JooYoung Seo, Ph.D. (he/him/his)
Assistant Professor, School of Information Sciences
Faculty Affiliate, National Center for Supercomputing Applications
Faculty Affiliate, Illinois Informatics Institute
University of Illinois Urbana-Champaign
Room 5158, 614 E. Daniel St.
Champaign, IL 61820
(217) 333-2671 | jseo1005 at illinois.edu<mailto:jseo1005 at illinois.edu>
ischool.illinois.edu/people/jooyoung-seo<https://ischool.illinois.edu/people/jooyoung-seo>

[University of Illinois logo]<http://illinois.edu/>

Under the Illinois Freedom of Information Act any written communication to or from university employees regarding university business is a public record and may be subject to public disclosure.

From: BlindRUG <blindrug-bounces at nfbnet.org<mailto:blindrug-bounces at nfbnet.org>> On Behalf Of Miso Kwak via BlindRUG
Sent: Thursday, September 14, 2023 5:42 PM
To: blindrug at nfbnet.org<mailto:blindrug at nfbnet.org>
Cc: misokwak12 at gmail.com<mailto:misokwak12 at gmail.com>
Subject: [BlindRUG] Trouble accessing output

Hello,
Disclaimer, I am new to using R.
I am using JAWS 2023 and running R through the Visual studio code.
I used to be able to readily access my output once I run the code by pressing shift tab, but I may have toggled something mistakenly or perhaps after the recent update to visual studio code, I seem to have to press ctrl + k followed by ctrl + ` in order to access my output now.
Is there any way I can access my output without this step?
Also, is it possible that my output may get cut off if I load a large data set?
Thank you in advance.
Miso
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/blindrug_nfbnet.org/attachments/20230915/00ea8922/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5363 bytes
Desc: image001.png
URL: <http://nfbnet.org/pipermail/blindrug_nfbnet.org/attachments/20230915/00ea8922/attachment.png>