<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)"><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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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"><div class=WordSection1><p class=MsoNormal>Hello, Jim,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></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.<o:p></o:p></p><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> NFBCS <nfbcs-bounces@nfbnet.org> <b>On Behalf Of </b>Jim Bauer via NFBCS<br><b>Sent:</b> Thursday, August 28, 2025 3:53 PM<br><b>To:</b> nfbcs@nfbnet.org<br><b>Cc:</b> Jim Bauer <holdsworthfan@eml.cc><br><b>Subject:</b> Re: [NFBCS] Help with GIT editors<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></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.<o:p></o:p></p></div><div><p class=MsoNormal>"git status" shows tracked/modified/etc. files in the repo.<o:p></o:p></p></div><div><p class=MsoNormal>Though old, the Git book has helped me:<o:p></o:p></p></div><div><p class=MsoNormal><a href="https://git-scm.com/book/en/v2">https://git-scm.com/book/en/v2</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>On 8/28/2025 8:36 AM, Ryan Stevens via NFBCS wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Hello,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></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?<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thanks and take care,<o:p></o:p></p><p class=MsoNormal>Ryan Stevens<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>NFBCS mailing list<o:p></o:p></pre><pre><a href="mailto:NFBCS@nfbnet.org">NFBCS@nfbnet.org</a><o:p></o:p></pre><pre><a href="http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org">http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org</a><o:p></o:p></pre><pre>To unsubscribe, change your list options or get your account info for NFBCS:<o:p></o:p></pre><pre><a href="http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/holdsworthfan%40eml.cc">http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/holdsworthfan%40eml.cc</a><o:p></o:p></pre></blockquote><p><o:p> </o:p></p></div></body></html>