<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Malgun Gothic";
panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
{font-family:"\@Malgun Gothic";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hello Robin and all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My apologies for this delayed response. It seems like robin raised two issues.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Q1: <span lang="EN-GB" style="mso-fareast-language:EN-US">As it stands, it seems that the cursor is placed at the start of the code that is sent to the terminal.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A1: I hear you, Robin. This issue seemed to be fixed in the latest VSCode insider version. What’s currently engineered in VSCode, the cursor location is always at the bottom of the executed result in the accessible buffer. Recent bug patches
were also made by VSCode team to address dynamic terminal buffer racing issue. The next stable version will provide you with a more pleasant experience.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Q2: <span lang="EN-GB" style="mso-fareast-language:EN-US">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.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A2: Yes, this is a bit buggy. However, terminal input edit field is getting better and it is now possible for screen reader users to navigate the console input and history via arrow keys. While composing this email, I have found some unstable
bugs to report. I will work with them to address this issue and will keep you all posted.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am considering hosting a Q&A session for VSCode with R sometime towards the end of this year. However, I need to work with VSCode team first to address some unstable issues before I officially introduce this alternative because there
have been some breaking changes in terminal buffer and key strokes and I don’t want to confuse anyone. I will share a blog posting first once these issues are addressed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All the best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JooYoung<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;vertical-align:baseline"><span style="color:black">--------------------<br>
</span><b><span style="color:#13294B">JooYoung Seo, Ph.D. (he/him/his)<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;vertical-align:baseline"><i><span style="color:#13294B">Assistant Professor,
</span></i><span style="color:#13294B">School of Information Sciences</span><span style="color:black"><br>
</span><i><span style="color:#13294B">Faculty Affiliate, </span></i><span style="color:#13294B">National Center for Supercomputing Applications</span><span style="color:black"><br>
</span><i><span style="color:#13294B">Faculty Affiliate, </span></i><span style="color:#13294B">Illinois Informatics Institute<b><o:p></o:p></b></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;vertical-align:baseline"><span style="color:#13294B">University of Illinois Urbana-Champaign</span><span style="color:black"><br>
</span><span style="color:#13294B">Room 5158, 614 E. Daniel St. </span><span style="color:black"><br>
</span><span style="color:#13294B">Champaign, IL 61820</span><span style="color:black"><br>
</span><span style="color:#13294B">(217) 333-2671 | </span><a href="mailto:jseo1005@illinois.edu"><span style="color:blue">jseo1005@illinois.edu</span></a><span style="color:black"><br>
</span><span style="color:#13294B"><a href="https://ischool.illinois.edu/people/jooyoung-seo"><span style="color:blue">ischool.illinois.edu/people/jooyoung-seo</span></a></span><span style="color:black"><br>
<br>
</span><a href="http://illinois.edu/"><span style="color:windowtext;text-decoration:none"><img border="0" width="165" height="43" style="width:1.7222in;height:.4444in" id="Picture_x0020_2" src="cid:image001.png@01D9EAC6.431C4290" alt="University of Illinois logo"></span></a><span style="color:black"><br>
<br>
</span><i><span style="color:#666666">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.</span></i><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> BlindRUG <blindrug-bounces@nfbnet.org> <b>On Behalf Of
</b>Robin Williams via BlindRUG<br>
<b>Sent:</b> Friday, September 15, 2023 9:42 AM<br>
<b>To:</b> Blind R Users Group <blindrug@nfbnet.org><br>
<b>Cc:</b> Robin Williams <Robin.Williams@atass-sports.co.uk><br>
<b>Subject:</b> Re: [BlindRUG] Trouble accessing output<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Thank you for these useful settings, JooYoung, and for your continuing work to improve the accessibility of VSCode.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">In general I am excited about using R in VSCode, and I hope to move to this IDE permanently in the future.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">All the best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Robin<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> BlindRUG <<a href="mailto:blindrug-bounces@nfbnet.org">blindrug-bounces@nfbnet.org</a>>
<b>On Behalf Of </b>Seo, JooYoung via BlindRUG<br>
<b>Sent:</b> Friday, September 15, 2023 1:24 AM<br>
<b>To:</b> Blind R Users Group <<a href="mailto:blindrug@nfbnet.org">blindrug@nfbnet.org</a>><br>
<b>Cc:</b> Seo, JooYoung <<a href="mailto:jseo1005@illinois.edu">jseo1005@illinois.edu</a>><br>
<b>Subject:</b> Re: [BlindRUG] Trouble accessing output<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal">Hello Miso,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">* Setting name: terminal.integrated.focusAfterRun<o:p></o:p></p>
<p class="MsoNormal">* Value: accessible-buffer <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">* Setting name: terminal.integrated.defaultLocation<o:p></o:p></p>
<p class="MsoNormal">* Setting value: view<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">* Setting name: r.source.focus<o:p></o:p></p>
<p class="MsoNormal">* Setting value: none<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To go back to your source editor, press ctrl+1.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hope this helps.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All the best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JooYoung<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;vertical-align:baseline"><span style="color:black">--------------------<br>
</span><b><span style="color:#13294B">JooYoung Seo, Ph.D. (he/him/his)<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;vertical-align:baseline"><i><span style="color:#13294B">Assistant Professor,
</span></i><span style="color:#13294B">School of Information Sciences</span><span style="color:black"><br>
</span><i><span style="color:#13294B">Faculty Affiliate, </span></i><span style="color:#13294B">National Center for Supercomputing Applications</span><span style="color:black"><br>
</span><i><span style="color:#13294B">Faculty Affiliate, </span></i><span style="color:#13294B">Illinois Informatics Institute<b><o:p></o:p></b></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;vertical-align:baseline"><span style="color:#13294B">University of Illinois Urbana-Champaign</span><span style="color:black"><br>
</span><span style="color:#13294B">Room 5158, 614 E. Daniel St. <br>
Champaign, IL 61820</span><span style="color:black"><br>
</span><span style="color:#13294B">(217) 333-2671 | </span><a href="mailto:jseo1005@illinois.edu"><span style="color:blue">jseo1005@illinois.edu</span></a><span style="color:black"><br>
</span><span style="color:#13294B"><a href="https://ischool.illinois.edu/people/jooyoung-seo"><span style="color:blue">ischool.illinois.edu/people/jooyoung-seo</span></a></span><span style="color:black"><br>
<br>
</span><a href="http://illinois.edu/"><span style="color:windowtext;text-decoration:none"><img border="0" width="165" height="43" style="width:1.7222in;height:.4444in" id="Picture_x0020_1" src="cid:image001.png@01D9EAC6.431C4290" alt="University of Illinois logo"></span></a><span style="color:black"><br>
<br>
</span><i><span style="color:#666666">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.</span></i><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> BlindRUG <<a href="mailto:blindrug-bounces@nfbnet.org">blindrug-bounces@nfbnet.org</a>>
<b>On Behalf Of </b>Miso Kwak via BlindRUG<br>
<b>Sent:</b> Thursday, September 14, 2023 5:42 PM<br>
<b>To:</b> <a href="mailto:blindrug@nfbnet.org">blindrug@nfbnet.org</a><br>
<b>Cc:</b> <a href="mailto:misokwak12@gmail.com">misokwak12@gmail.com</a><br>
<b>Subject:</b> [BlindRUG] Trouble accessing output<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal">Disclaimer, I am new to using R.<o:p></o:p></p>
<p class="MsoNormal">I am using JAWS 2023 and running R through the Visual studio code.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">Is there any way I can access my output without this step?<o:p></o:p></p>
<p class="MsoNormal">Also, is it possible that my output may get cut off if I load a large data set?<o:p></o:p></p>
<p class="MsoNormal">Thank you in advance.<o:p></o:p></p>
<p class="MsoNormal">Miso<o:p></o:p></p>
</div>
</body>
</html>