<div><div>I've never felt the need to install JAWS scripts to run VSCode, and I use it with both JAWS and NVDA.</div><div dir="auto"><br></div><div dir="auto">As for whether you should use Visual Studio or VSCode, that probably depends on what sort of development you're doing.</div><div dir="auto"><br></div><div dir="auto">If you've got Git running on your commandline, that's probably the best way to master Git. VSCode can make it easier, because it gives you a GUI, but if you don't know what the GUI is doing behind the scenes, it may be more confusing than helpful.</div></div><div dir="auto"><br></div><div dir="auto">Good luck.</div><div dir="auto"><br></div><div dir="auto">Aaron</div><div dir="auto"><br></div><div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Wed, Sep 3, 2025 at 08:12 Ryan Stevens via NFBCS <<a href="mailto:nfbcs@nfbnet.org" target="_blank">nfbcs@nfbnet.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal">Hi, Aaron,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I\u2019ve installed VS Code and found a book on Bookshare to learn it. I also Googled using VS Code with JAWS and I\u2019m seeing results that say JAWS scripts need to be installed. Is this the case, and how safe is doing so?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Also, I\u2019ve worked with Visual Studio .net for years and I see that it, too, can work with GIT. Which of the two is preferable, if either?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Finally, since I\u2019m a newbie with GIT, I was using Windows Command Line and GIT Bash to enter commands to learn the syntax. All of this is a bit overwhelming, and I could use some advice on what a good \u201cstep 1\u201d is.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks,<u></u><u></u></p><p class="MsoNormal"> Ryan<u></u><u></u></p></div></div><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><b>From:</b> NFBCS <<a href="mailto:nfbcs-bounces@nfbnet.org" target="_blank">nfbcs-bounces@nfbnet.org</a>> <b>On Behalf Of </b>Aaron Cannon via NFBCS<br><b>Sent:</b> Friday, August 29, 2025 4:42 PM<br><b>To:</b> NFB in Computer Science Mailing List <<a href="mailto:nfbcs@nfbnet.org" target="_blank">nfbcs@nfbnet.org</a>><br><b>Cc:</b> Aaron Cannon <<a href="mailto:cannona@fireantproductions.com" target="_blank">cannona@fireantproductions.com</a>><br><b>Subject:</b> Re: [NFBCS] Help with GIT editors<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">Yes, Elijah is correct. VSCode should be in your path, so you can just do code, but make sure you pass the --wait flag, or git may not know when you're done editing the file. Then when done, save the file and close the window so Git will know you're done.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">To answer a different question you asked, yes, it's always worth learning VSCode! It is a game changer.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Aaron<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">On Fri, Aug 29, 2025 at 14:26 Elijah Massey via NFBCS <<a href="mailto:nfbcs@nfbnet.org" target="_blank">nfbcs@nfbnet.org</a>> wrote:<u></u><u></u></p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"><div><p class="MsoNormal">The way GIT commit editing works is Git launches an external editor program to edit the message; Git doesn't have its own editor. In your case its probably launching vi or nano, since from the behavior you described its launching a terminal editor. Try running "git config --global "core.editor" notepad --wait", and then make a commit. It should open Notepad and let you type a commit message there; instead of using vi or nanno as its editor, Git will use Notepad. If VS Code is in your PATH environment variable, then using "code" instead of "notepad" will also work, although I'm not sure if VS Code is added to PATH by default on Windows.<u></u><u></u></p><div><p class="MsoNormal">Sent from my iPhone<u></u><u></u></p></div><div><p class="MsoNormal"><br><br><u></u><u></u></p><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal" style="margin-bottom:12.0pt">On Aug 29, 2025, at 14:14, Ryan Stevens via NFBCS <<a href="mailto:nfbcs@nfbnet.org" target="_blank">nfbcs@nfbnet.org</a>> wrote:<u></u><u></u></p></blockquote></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">\ufeff<u></u><u></u></p></div></blockquote></div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><p class="MsoNormal">Hello, Jim,<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Thanks for your response. My main concern is being able to place comments in the commit editor (and possibly the revert editor) in a terminal window. I found a keyboard short cut to cleanly enter the comment (Alt-G, C), but I\u2019m still stuck trying to save it and return to the command line. Are you aware of any, and would switching to VSCode simplify the process? Thanks.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>From:</b> NFBCS <<a href="mailto:nfbcs-bounces@nfbnet.org" target="_blank">nfbcs-bounces@nfbnet.org</a>> <b>On Behalf Of </b>Jim Bauer via NFBCS<br><b>Sent:</b> Thursday, August 28, 2025 3:53 PM<br><b>To:</b> <a href="mailto:nfbcs@nfbnet.org" target="_blank">nfbcs@nfbnet.org</a><br><b>Cc:</b> Jim Bauer <<a href="mailto:holdsworthfan@eml.cc" target="_blank">holdsworthfan@eml.cc</a>><br><b>Subject:</b> Re: [NFBCS] Help with GIT editors<u></u><u></u></p></div></div><p class="MsoNormal"> <u></u><u></u></p><div><p class="MsoNormal">You can change the git editor with the "core.editor" config option. For example, "git config --global core.editor code --wait" sets vscode as the default git editor everywhere.<u></u><u></u></p></div><div><p class="MsoNormal">"git status" shows tracked/modified/etc. files in the repo.<u></u><u></u></p></div><div><p class="MsoNormal">Though old, the Git book has helped me:<u></u><u></u></p></div><div><p class="MsoNormal"><a href="https://git-scm.com/book/en/v2" target="_blank">https://git-scm.com/book/en/v2</a><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">On 8/28/2025 8:36 AM, Ryan Stevens via NFBCS wrote:<u></u><u></u></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Hello,<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">My company is moving to GIT as our source control after years on SourceGear Vault. I have been learning and working with GIT on Windows Command Line and GIT Bash relatively easily, but there are a couple of snags. First, committing and reverting code require a message/description, and trying to enter them doesn\u2019t seem to be working properly, and I get stuck in the commit editor. I do use the -m parameter in the commit command to get around this, but I don\u2019t always remember to do so. For revert, it looks like I need to use the --no-commit parameter, then run a commit -m. Second, the training books point out that filenames appear in different colors based on their status, and I have no idea how to check that in the terminal window. I use the latest version of JAWS, and I\u2019m wondering if there are keyboard shortcuts for these issues. Alternatively, are there other GIT editors that are accessible and handle these problems?<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Thanks and take care,<u></u><u></u></p><p class="MsoNormal">Ryan Stevens<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><pre>_______________________________________________<u></u><u></u></pre><pre>NFBCS mailing list<u></u><u></u></pre><pre><a href="mailto:NFBCS@nfbnet.org" target="_blank">NFBCS@nfbnet.org</a><u></u><u></u></pre><pre><a href="http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org" target="_blank">http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org</a><u></u><u></u></pre><pre>To unsubscribe, change your list options or get your account info for NFBCS:<u></u><u></u></pre><pre><a href="http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/holdsworthfan%40eml.cc" target="_blank">http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/holdsworthfan%40eml.cc</a><u></u><u></u></pre></blockquote><p> <u></u><u></u></p></div><p class="MsoNormal">_______________________________________________<br>NFBCS mailing list<br><a href="mailto:NFBCS@nfbnet.org" target="_blank">NFBCS@nfbnet.org</a><br><a href="http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org" target="_blank">http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org</a><br>To unsubscribe, change your list options or get your account info for NFBCS:<u></u><u></u></p></div></blockquote></div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal"><a href="http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/emassey0135%40gmail.com" target="_blank">http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/emassey0135%40gmail.com</a><u></u><u></u></p></div></blockquote></div><p class="MsoNormal">_______________________________________________<br>NFBCS mailing list<br><a href="mailto:NFBCS@nfbnet.org" target="_blank">NFBCS@nfbnet.org</a><br><a href="http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org" target="_blank">http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org</a><br>To unsubscribe, change your list options or get your account info for NFBCS:<br><a href="http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com" target="_blank">http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com</a><u></u><u></u></p></blockquote></div></div></div></div>_______________________________________________<br>
NFBCS mailing list<br>
<a href="mailto:NFBCS@nfbnet.org" target="_blank">NFBCS@nfbnet.org</a><br>
<a href="http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org" rel="noreferrer" target="_blank">http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org</a><br>
To unsubscribe, change your list options or get your account info for NFBCS:<br>
<a href="http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com" rel="noreferrer" target="_blank">http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com</a><br>
</blockquote></div></div>
</div>