Hi, I too have moved to the built-in SSH client for most things now. Overall it works pretty well. I just get tired of changing cursors back and forth to review output of large data sets. It would be nice if tabbed data could be reviewed like a table, but I don’t think there is an easy way to make that work. Working with Nano or VI does present a unique challenge never the less. -----Original Message----- From: Simon Eigeldinger <simon.eigeldinger@vol.at> Sent: Wednesday, July 17, 2019 11:31 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org>; Andrew Hodgson <andrew@hodgson.io> Subject: [Blind-sysadmins] Re: the ultimate terminal experience Hi, Same here. I created various batch files that start various servers. so you can run multiple connections at once. Greetings, Simon Am 17.07.2019 um 11:24 schrieb Andrew Hodgson:
Hi,
Echoing what Steve said. In addition I don't know whether anyone has tried this but I have moved away from PuTTY and other SSH clients on Windows now to the built-in SSH client. It works really well in my opinion and is just like being in the command prompt.
Andrew. ________________________________________ From: Steve Matzura [sm@noisynotes.com] Sent: 16 July 2019 23:40 To: blind-sysadmins@lists.hodgsonfamily.org Subject: [Blind-sysadmins] Re: the ultimate terminal experience
I think the most important thing in an accessible terminal program is for the computer and screenreader cursor to be as tightly locked to the terminal cursor as is programatically possible. I go back to the deep dark DOS days, and I remember terminal emulators like ProComm were excellent at this, no matter what screenreader was being used with them. Most of my workaday tasks were done using this facility. I always knew where my cursor was, I could move it around the terminal emulation window just as if I were moving it around a word-processor document, the terminal cursor never unbound from the computer/screenreader cursor. I've never had that kind of experience with a Windows terminal emulator. Some have come closer than others, but there's always some lag between the two halves of the system, or the screenreader voices something on which the terminal/computer cursor is not focused. If that problem could be solved, it'd be just the best thing.
On 7/16/2019 2:48 PM, Ryan Shugart via Blind-sysadmins wrote:
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
--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org