I spend a lot of time editing files remotely in vim and working in a remote shell. It would be very helpful if these things are supported using the standard Windows ssh client. Currently I'm using Secure CRT, which works well enough. Favorite features of that client are: tree structure for sessions so I can quickly select one without having to type a hostname, ability to organize related sessions so I can ctrl+tab between them, and ability to quickly copy screen/buffer contents and paste into an editor to work with the text. The first feature could be generalized as "a tree for organizing and selecting command aliases". Chris On Tue, Jul 16, 2019 at 10:51:53PM +0000, Ryan Shugart via Blind-sysadmins wrote:
Hi: For those of you who want the "messenger" approach, how would you want full screen apps to be handled, apps like VI and/or Emacs that move the cursor around and draw things in different parts of the screen? Do you use an editor on the remote machine or edit on your local machine and upload? Ryan
-----Original Message----- From: Anatoliy Shudrya <anatoliyshudrya@hotmail.com> Sent: Tuesday, July 16, 2019 12:42 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Re: the ultimate terminal experience
I'd love to be able to use error keys and review output of commands without using JAWS cursor or any other complicated ways to read the terminal screen. It is also very important to be able to read word by word, character by character not only line by line or block by block. Select, copy and paste all comes in handy in the typing line and in the output screen. All sounds like basics, but some of these basics have been missing in command line and PowerShell. Messenger style terminal sounds like a very good idea, type commands in the typing box and review them by shift tab and error keys in the review window. Maybe instead of messenger style terminal, to have a command mode to activate and type commands and when done with command, deactivate command mode and review the output with error keys, just an idea.
I am glad to hear this is being worked on. Thank you
-----Original Message----- From: Ryan Shugart via Blind-sysadmins <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, July 16, 2019 11:49 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Cc: Ryan Shugart <ryshugar@microsoft.com> Subject: [Blind-sysadmins] the ultimate terminal experience
Hello everyone: I wanted to throw a question out to everyone. As we are working with the new Windows Terminal product to insure it is accessible and works well with assistive technologies, I wanted to reach out to this list and find out what would be the ideal terminal experience for you? What would you be looking for and want in a new terminal program from an accessibility standpoint, something that would set it aside from the rest and really make it an enjoyable experience to use, not just something you can use? I'm definitely going to bring the feedback to the Windows Terminal team, and while I can't guarantee it will all be acted on, it will certainly help set a direction and way to move forward. Thanks much. Ryan
Ryan Shugart Program Manager II, Cloud+AI Accessibility Microsoft Corporation 425-705-1262
_______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org