[NFBCS] best solution for remote linux terminal work

[Chris Nestrud]

If you're going for a totally command-line terminal solution, I suspect
using the Windows 10 command-line ssh client (available from optional
features in control panel) would work well and would be comparable to
setting up a separate Linux box or VM.

I personally like JAWS and Secure CRT for the cursor tracking, GUI for keeping
track of many ssh connections, tabbed windows, easy port forwarding
setup, jump server support, etc. I spend a lot of time editing files in
vim, using full-screen programs like top, working in a shell, etc. with
no issues. This includes a lot of copying command output to paste
elsewhere and pasting into shells.

Chris

On Fri, Aug 07, 2020 at 12:55:39PM -0600, Ryan Boudwin via NFBCS wrote:
> I'd also need to be able to use web applications and copy and paste
> terminal output into JIRA; I'm concerned with how well that would work on a
> linux-only box. I haven't used a linux screen reader before but I have
> heard it's not the best experience.
> 
> Best regards,
> 
> Ryan Boudwin
> ryanboudwin at gmail.com
> 
> 
> 
> On Fri, Aug 7, 2020 at 12:40 PM Brian Buhrow <buhrow at nfbcal.org> wrote:
> 
> >         hello.  As a long time Unix person who uses terminals over ssh on a
> > daily basis with screen readers, I strongly recommend you build yourself a
> > Linux box and ssh to your remote sites from there.  Then, you can either
> > use Speakup or Yasr as your screen reader.  I use Yasr with the
> > eflite/flite
> > software speech engine.  This combination of software will give you full
> > access to screen oriented programs in terminal environments.  While I think
> > things are changing a bit, terminal access using Jaws, NVDA or VoiceOver
> > is, in my experience, doable, but very very suboptimal.  As proof of that,
> > you'll  probably get a number of folks writing back on this question
> > suggesting that terminal access works fine using the Windows screen
> > readers, but that you'll find it easier to edit files on the local Windows
> > machine and then transfer them up using scp or some other file transfer
> > protocol once you're done.  that is a very inefficient way to edit files on
> > remote servers.  The combination of software I suggest lets me edit files
> > with ease in their native environments on the servers on which they belong.
> >
> > Hope this helps.
> > -Brian
> >
> > On Aug 7, 11:59am, Ryan Boudwin via NFBCS wrote:
> > } Subject: [NFBCS] best solution for remote linux terminal work
> > } Hey folks,
> > }
> > } I am considering a return to a technical individual contributor role. The
> > } job requires a significant amount of terminal work, over SSH to remote
> > } linux servers.
> > }
> > } What OS/screen reader/ssh client combination is the best/easiest/most
> > } reliable to use? I have access to JAWS, NVDA or Voiceover as needed but I
> > } haven't done terminal work since my blindness hit.
> > }
> > } Best regards,
> > }
> > } Ryan Boudwin
> > } ryanboudwin at gmail.com
> > } _______________________________________________
> > } NFBCS mailing list
> > } NFBCS at nfbnet.org
> > } http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> > } To unsubscribe, change your list options or get your account info for
> > NFBCS:
> > }
> > http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/buhrow%40lothlorien.nfbcal.org
> > >-- End of excerpt from Ryan Boudwin via NFBCS
> >
> >
> >
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ccn%40chrisnestrud.com