Topics

SSH with the new windows Bash Client?


 

Hello,
Has anyone managed to give the new windows bash client a try yet? I am waiting for my update to install. It is a very functional Ubuntu type system and that means that SSH should work.
If that is the case, no more needing to deal with partly accessible SSH clients, we will be able to use the default windows client!
Thanks,


jeremy <icu8it2@...>
 

If it's the same thing that was mentioned a while ago here on list, it does work, but seems to have some of the same issues in navigating things like ncurses menus and areas such as files within nano. As with Teraterm and I assume, putty, NVDA doesn't always track the cursor correctly, so you have to use review commands to get an idea of your position sometimes. I'm not sure if this is mostly specific to recent versions of NVDA, as I know older versions worked really well with Teraterm, but I do know the latest one can be really frustrating to use with it.

How does one go about getting and using this bash console in 10, btw, as I'd certainly be willing to give it a shot. Is it something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try yet? I am waiting for my update to install. It is a very functional Ubuntu type system and that means that SSH should work.
If that is the case, no more needing to deal with partly accessible SSH clients, we will be able to use the default windows client!
Thanks,



 

Hello,
So I was able to get the bash client working on my computer.
Pros:
The client works great, it is just like powershell or command prompt.
2. SSH works OK. You can read what happened with the review cursor, but there is a huge lag when typing (nvda will say the letter like half a second after you type and it is not 100%). There is no feedback for up arrow to retype commands and no feedback when letters are deleted.
Other than that things are really good! Vim could use some tweaking to be a little easier to use, but it is the best. Nano doesn't like opening existing files. NVDA doesn't read anything when you open an already existing file with nano.

Because this is pretty much a commandline, is NVDA able to modify any of these behaviors?
It would be beyond amazing if there was a text editor that had the usability of EdSharp on the bash line. Vim could be that, but I have not seen anything to show me it is faster than editing with EdSharp. Apparently it is not normal for most people to never leave their keyboard when they are typing and that is what Vim allows. But EdSharp has even faster key commands and it is a lot more user friendly.

Thanks,

On Fri, Aug 19, 2016 at 2:14 PM, Jeremy <icu8it2@...> wrote:
If it's the same thing that was mentioned a while ago here on list, it does work, but seems to have some of the same issues in navigating things like ncurses menus and areas such as files within nano. As with Teraterm and I assume, putty, NVDA doesn't always track the cursor correctly, so you have to use review commands to get an idea of your position sometimes. I'm not sure if this is mostly specific to recent versions of NVDA, as I know older versions worked really well with Teraterm, but I do know the latest one can be really frustrating to use with it.

How does one go about getting and using this bash console in 10, btw, as I'd certainly be willing to give it a shot. Is it something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try yet? I am waiting for my update to install. It is a very functional Ubuntu type system and that means that SSH should work.
If that is the case, no more needing to deal with partly accessible SSH clients, we will be able to use the default windows client!
Thanks,




jeremy <icu8it2@...>
 

I've only been on 10 for a week or so, so I'll have to play with the command line more to get an idea how it's working with NVDA, but at least on 7, NVDA seemed to read a bit more than it seems to be reading for you. At least with reading the command history, moving back and forth through the edit area to review character by character, this all worked pretty well. I've also never really ran into any lag on 7, but that wasn't using any type of a network connection either.

I can't recall who it was or even when exactly the message was posted, but I don't remember he/she saying there was issues with lag, reading command history, etc, just mostly that it was similar to the problems we seem to have in programs like putty, moving through applications like nano and vim, or trying to move up and down in ncurses type menus.

Perhaps it was here, a long while ago that somewhat of a discussion had been brought up to give some explanations on why NVDA and other Windows screenreaders seem to crap out in programs like the command prompt, why they don't track correctly in menus there, keep track of a cursor, etc, but I don't remember everything that was said. I do know though that the size of the window, shape of the cursor, number of lines in that window and number of allowed characters per line used to be really important in getting JFW set up for TeraTerm and then it worked considerably better.

All the same, thanks for the link to an introduction to bash, as I'm sure that it will be of help for sure, but I was more asking how one goes about enabling the bash terminal on 10 or if it came automatically. hehe :)
It's my luck that it's right in front of my face and I'm just missing it, but there's still quite a lot that I haven't explored on 10. haha
Here's hoping our wonderful devs may just put a little sweet sweet love towards the terminal and get it working as well as NVDA does on lots of other applications, as having a terminal that's easy to enable and we can use to ssh into those types of systems, that would be totally sweet.
Take care.

On 8/20/2016 10:39 AM, Brandon Keith Biggs wrote:
Hello,
So I was able to get the bash client working on my computer.
Pros:
The client works great, it is just like powershell or command prompt.
2. SSH works OK. You can read what happened with the review cursor, but there is a huge lag when typing (nvda will say the letter like half a second after you type and it is not 100%). There is no feedback for up arrow to retype commands and no feedback when letters are deleted.
Other than that things are really good! Vim could use some tweaking to be a little easier to use, but it is the best. Nano doesn't like opening existing files. NVDA doesn't read anything when you open an already existing file with nano.

Because this is pretty much a commandline, is NVDA able to modify any of these behaviors?
It would be beyond amazing if there was a text editor that had the usability of EdSharp on the bash line. Vim could be that, but I have not seen anything to show me it is faster than editing with EdSharp. Apparently it is not normal for most people to never leave their keyboard when they are typing and that is what Vim allows. But EdSharp has even faster key commands and it is a lot more user friendly.

Here is a guide on how to get started with the bash prompt:
http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/

Thanks,



On Fri, Aug 19, 2016 at 2:14 PM, Jeremy <icu8it2@...> wrote:
If it's the same thing that was mentioned a while ago here on list, it does work, but seems to have some of the same issues in navigating things like ncurses menus and areas such as files within nano. As with Teraterm and I assume, putty, NVDA doesn't always track the cursor correctly, so you have to use review commands to get an idea of your position sometimes. I'm not sure if this is mostly specific to recent versions of NVDA, as I know older versions worked really well with Teraterm, but I do know the latest one can be really frustrating to use with it.

How does one go about getting and using this bash console in 10, btw, as I'd certainly be willing to give it a shot. Is it something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try yet? I am waiting for my update to install. It is a very functional Ubuntu type system and that means that SSH should work.
If that is the case, no more needing to deal with partly accessible SSH clients, we will be able to use the default windows client!
Thanks,





 

Hello,
As I remember, PUTTY is really hard to use with NVDA. I never liked it and always avoided using SSH if I could.
But this is a windows thing, so if we all push for it to be made really accessible it may really happen. You can vote for it:
https://microsoftaccessibility.uservoice.com/forums/307429-microsoft-accessibility-feedback/suggestions/15734662-make-the-command-lines-work-better-with-screen-rea


The link I gave talked about how to install the bash client.
Thanks,

On Sat, Aug 20, 2016 at 8:46 PM, Jeremy <icu8it2@...> wrote:
I've only been on 10 for a week or so, so I'll have to play with the command line more to get an idea how it's working with NVDA, but at least on 7, NVDA seemed to read a bit more than it seems to be reading for you. At least with reading the command history, moving back and forth through the edit area to review character by character, this all worked pretty well. I've also never really ran into any lag on 7, but that wasn't using any type of a network connection either.

I can't recall who it was or even when exactly the message was posted, but I don't remember he/she saying there was issues with lag, reading command history, etc, just mostly that it was similar to the problems we seem to have in programs like putty, moving through applications like nano and vim, or trying to move up and down in ncurses type menus.

Perhaps it was here, a long while ago that somewhat of a discussion had been brought up to give some explanations on why NVDA and other Windows screenreaders seem to crap out in programs like the command prompt, why they don't track correctly in menus there, keep track of a cursor, etc, but I don't remember everything that was said. I do know though that the size of the window, shape of the cursor, number of lines in that window and number of allowed characters per line used to be really important in getting JFW set up for TeraTerm and then it worked considerably better.

All the same, thanks for the link to an introduction to bash, as I'm sure that it will be of help for sure, but I was more asking how one goes about enabling the bash terminal on 10 or if it came automatically. hehe :)
It's my luck that it's right in front of my face and I'm just missing it, but there's still quite a lot that I haven't explored on 10. haha
Here's hoping our wonderful devs may just put a little sweet sweet love towards the terminal and get it working as well as NVDA does on lots of other applications, as having a terminal that's easy to enable and we can use to ssh into those types of systems, that would be totally sweet.
Take care.

On 8/20/2016 10:39 AM, Brandon Keith Biggs wrote:
Hello,
So I was able to get the bash client working on my computer.
Pros:
The client works great, it is just like powershell or command prompt.
2. SSH works OK. You can read what happened with the review cursor, but there is a huge lag when typing (nvda will say the letter like half a second after you type and it is not 100%). There is no feedback for up arrow to retype commands and no feedback when letters are deleted.
Other than that things are really good! Vim could use some tweaking to be a little easier to use, but it is the best. Nano doesn't like opening existing files. NVDA doesn't read anything when you open an already existing file with nano.

Because this is pretty much a commandline, is NVDA able to modify any of these behaviors?
It would be beyond amazing if there was a text editor that had the usability of EdSharp on the bash line. Vim could be that, but I have not seen anything to show me it is faster than editing with EdSharp. Apparently it is not normal for most people to never leave their keyboard when they are typing and that is what Vim allows. But EdSharp has even faster key commands and it is a lot more user friendly.

Here is a guide on how to get started with the bash prompt:
http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/

Thanks,



On Fri, Aug 19, 2016 at 2:14 PM, Jeremy <icu8it2@...> wrote:
If it's the same thing that was mentioned a while ago here on list, it does work, but seems to have some of the same issues in navigating things like ncurses menus and areas such as files within nano. As with Teraterm and I assume, putty, NVDA doesn't always track the cursor correctly, so you have to use review commands to get an idea of your position sometimes. I'm not sure if this is mostly specific to recent versions of NVDA, as I know older versions worked really well with Teraterm, but I do know the latest one can be really frustrating to use with it.

How does one go about getting and using this bash console in 10, btw, as I'd certainly be willing to give it a shot. Is it something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try yet? I am waiting for my update to install. It is a very functional Ubuntu type system and that means that SSH should work.
If that is the case, no more needing to deal with partly accessible SSH clients, we will be able to use the default windows client!
Thanks,






jeremy <icu8it2@...>
 

Oops, my bad. I hadn't read all the way through the link before I'd written the message, my mistake. Thanks for the instructions. :)
Tc.

On 8/21/2016 4:50 AM, Brandon Keith Biggs wrote:
Hello,
As I remember, PUTTY is really hard to use with NVDA. I never liked it and always avoided using SSH if I could.
But this is a windows thing, so if we all push for it to be made really accessible it may really happen. You can vote for it:
https://microsoftaccessibility.uservoice.com/forums/307429-microsoft-accessibility-feedback/suggestions/15734662-make-the-command-lines-work-better-with-screen-rea


The link I gave talked about how to install the bash client.
Thanks,



On Sat, Aug 20, 2016 at 8:46 PM, Jeremy <icu8it2@...> wrote:
I've only been on 10 for a week or so, so I'll have to play with the command line more to get an idea how it's working with NVDA, but at least on 7, NVDA seemed to read a bit more than it seems to be reading for you. At least with reading the command history, moving back and forth through the edit area to review character by character, this all worked pretty well. I've also never really ran into any lag on 7, but that wasn't using any type of a network connection either.

I can't recall who it was or even when exactly the message was posted, but I don't remember he/she saying there was issues with lag, reading command history, etc, just mostly that it was similar to the problems we seem to have in programs like putty, moving through applications like nano and vim, or trying to move up and down in ncurses type menus.

Perhaps it was here, a long while ago that somewhat of a discussion had been brought up to give some explanations on why NVDA and other Windows screenreaders seem to crap out in programs like the command prompt, why they don't track correctly in menus there, keep track of a cursor, etc, but I don't remember everything that was said. I do know though that the size of the window, shape of the cursor, number of lines in that window and number of allowed characters per line used to be really important in getting JFW set up for TeraTerm and then it worked considerably better.

All the same, thanks for the link to an introduction to bash, as I'm sure that it will be of help for sure, but I was more asking how one goes about enabling the bash terminal on 10 or if it came automatically. hehe :)
It's my luck that it's right in front of my face and I'm just missing it, but there's still quite a lot that I haven't explored on 10. haha
Here's hoping our wonderful devs may just put a little sweet sweet love towards the terminal and get it working as well as NVDA does on lots of other applications, as having a terminal that's easy to enable and we can use to ssh into those types of systems, that would be totally sweet.
Take care.

On 8/20/2016 10:39 AM, Brandon Keith Biggs wrote:
Hello,
So I was able to get the bash client working on my computer.
Pros:
The client works great, it is just like powershell or command prompt.
2. SSH works OK. You can read what happened with the review cursor, but there is a huge lag when typing (nvda will say the letter like half a second after you type and it is not 100%). There is no feedback for up arrow to retype commands and no feedback when letters are deleted.
Other than that things are really good! Vim could use some tweaking to be a little easier to use, but it is the best. Nano doesn't like opening existing files. NVDA doesn't read anything when you open an already existing file with nano.

Because this is pretty much a commandline, is NVDA able to modify any of these behaviors?
It would be beyond amazing if there was a text editor that had the usability of EdSharp on the bash line. Vim could be that, but I have not seen anything to show me it is faster than editing with EdSharp. Apparently it is not normal for most people to never leave their keyboard when they are typing and that is what Vim allows. But EdSharp has even faster key commands and it is a lot more user friendly.

Here is a guide on how to get started with the bash prompt:
http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/

Thanks,



On Fri, Aug 19, 2016 at 2:14 PM, Jeremy <icu8it2@...> wrote:
If it's the same thing that was mentioned a while ago here on list, it does work, but seems to have some of the same issues in navigating things like ncurses menus and areas such as files within nano. As with Teraterm and I assume, putty, NVDA doesn't always track the cursor correctly, so you have to use review commands to get an idea of your position sometimes. I'm not sure if this is mostly specific to recent versions of NVDA, as I know older versions worked really well with Teraterm, but I do know the latest one can be really frustrating to use with it.

How does one go about getting and using this bash console in 10, btw, as I'd certainly be willing to give it a shot. Is it something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try yet? I am waiting for my update to install. It is a very functional Ubuntu type system and that means that SSH should work.
If that is the case, no more needing to deal with partly accessible SSH clients, we will be able to use the default windows client!
Thanks,







Simone Dal Maso
 

I don't agree.
Putty and Cygwin are usable, and on cygwin you have no problem with arrow keys.
And for bash, nano is working ok, NVDA read what you want, at least on my pc!

Il 21/08/2016 23:15, Jeremy ha scritto:
Oops, my bad. I hadn't read all the way through the link before I'd
written the message, my mistake. Thanks for the instructions. :)
Tc.
On 8/21/2016 4:50 AM, Brandon Keith Biggs wrote:
Hello,
As I remember, PUTTY is really hard to use with NVDA. I never liked it
and always avoided using SSH if I could.
But this is a windows thing, so if we all push for it to be made
really accessible it may really happen. You can vote for it:
https://microsoftaccessibility.uservoice.com/forums/307429-microsoft-accessibility-feedback/suggestions/15734662-make-the-command-lines-work-better-with-screen-rea


The link I gave talked about how to install the bash client.
Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>

On Sat, Aug 20, 2016 at 8:46 PM, Jeremy <icu8it2@...
<mailto:icu8it2@...>> wrote:

I've only been on 10 for a week or so, so I'll have to play with
the command line more to get an idea how it's working with NVDA,
but at least on 7, NVDA seemed to read a bit more than it seems to
be reading for you. At least with reading the command history,
moving back and forth through the edit area to review character by
character, this all worked pretty well. I've also never really ran
into any lag on 7, but that wasn't using any type of a network
connection either.

I can't recall who it was or even when exactly the message was
posted, but I don't remember he/she saying there was issues with
lag, reading command history, etc, just mostly that it was similar
to the problems we seem to have in programs like putty, moving
through applications like nano and vim, or trying to move up and
down in ncurses type menus.

Perhaps it was here, a long while ago that somewhat of a
discussion had been brought up to give some explanations on why
NVDA and other Windows screenreaders seem to crap out in programs
like the command prompt, why they don't track correctly in menus
there, keep track of a cursor, etc, but I don't remember
everything that was said. I do know though that the size of the
window, shape of the cursor, number of lines in that window and
number of allowed characters per line used to be really important
in getting JFW set up for TeraTerm and then it worked considerably
better.

All the same, thanks for the link to an introduction to bash, as
I'm sure that it will be of help for sure, but I was more asking
how one goes about enabling the bash terminal on 10 or if it came
automatically. hehe :)
It's my luck that it's right in front of my face and I'm just
missing it, but there's still quite a lot that I haven't explored
on 10. haha
Here's hoping our wonderful devs may just put a little sweet sweet
love towards the terminal and get it working as well as NVDA does
on lots of other applications, as having a terminal that's easy to
enable and we can use to ssh into those types of systems, that
would be totally sweet.
Take care.

On 8/20/2016 10:39 AM, Brandon Keith Biggs wrote:
Hello,
So I was able to get the bash client working on my computer.
Pros:
The client works great, it is just like powershell or command prompt.
2. SSH works OK. You can read what happened with the review
cursor, but there is a huge lag when typing (nvda will say the
letter like half a second after you type and it is not 100%).
There is no feedback for up arrow to retype commands and no
feedback when letters are deleted.
Other than that things are really good! Vim could use some
tweaking to be a little easier to use, but it is the best. Nano
doesn't like opening existing files. NVDA doesn't read anything
when you open an already existing file with nano.

Because this is pretty much a commandline, is NVDA able to modify
any of these behaviors?
It would be beyond amazing if there was a text editor that had
the usability of EdSharp on the bash line. Vim could be that, but
I have not seen anything to show me it is faster than editing
with EdSharp. Apparently it is not normal for most people to
never leave their keyboard when they are typing and that is what
Vim allows. But EdSharp has even faster key commands and it is a
lot more user friendly.

Here is a guide on how to get started with the bash prompt:
http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/
<http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/>

Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>

On Fri, Aug 19, 2016 at 2:14 PM, Jeremy
<<mailto:icu8it2@...>icu8it2@...> wrote:

If it's the same thing that was mentioned a while ago here on
list, it does work, but seems to have some of the same issues
in navigating things like ncurses menus and areas such as
files within nano. As with Teraterm and I assume, putty, NVDA
doesn't always track the cursor correctly, so you have to use
review commands to get an idea of your position sometimes.
I'm not sure if this is mostly specific to recent versions of
NVDA, as I know older versions worked really well with
Teraterm, but I do know the latest one can be really
frustrating to use with it.

How does one go about getting and using this bash console in
10, btw, as I'd certainly be willing to give it a shot. Is it
something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try
yet? I am waiting for my update to install. It is a very
functional Ubuntu type system and that means that SSH should
work.
If that is the case, no more needing to deal with partly
accessible SSH clients, we will be able to use the default
windows client!
Thanks,

Brandon Keith Biggs <http://brandonkeithbiggs.com/>


mattias
 

but forgot to copy and paste

sometimes you need to do that


Den 2016-08-22 kl. 09:23, skrev Simone Dal Maso:

I don't agree.
Putty and Cygwin are usable, and on cygwin you have no problem with arrow keys.
And for bash, nano is working ok, NVDA read what you want, at least on my pc!


Il 21/08/2016 23:15, Jeremy ha scritto:
Oops, my bad. I hadn't read all the way through the link before I'd
written the message, my mistake. Thanks for the instructions. :)
Tc.
On 8/21/2016 4:50 AM, Brandon Keith Biggs wrote:
Hello,
As I remember, PUTTY is really hard to use with NVDA. I never liked it
and always avoided using SSH if I could.
But this is a windows thing, so if we all push for it to be made
really accessible it may really happen. You can vote for it:
https://microsoftaccessibility.uservoice.com/forums/307429-microsoft-accessibility-feedback/suggestions/15734662-make-the-command-lines-work-better-with-screen-rea


The link I gave talked about how to install the bash client.
Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>

On Sat, Aug 20, 2016 at 8:46 PM, Jeremy <icu8it2@...
<mailto:icu8it2@...>> wrote:

I've only been on 10 for a week or so, so I'll have to play with
the command line more to get an idea how it's working with NVDA,
but at least on 7, NVDA seemed to read a bit more than it seems to
be reading for you. At least with reading the command history,
moving back and forth through the edit area to review character by
character, this all worked pretty well. I've also never really ran
into any lag on 7, but that wasn't using any type of a network
connection either.

I can't recall who it was or even when exactly the message was
posted, but I don't remember he/she saying there was issues with
lag, reading command history, etc, just mostly that it was similar
to the problems we seem to have in programs like putty, moving
through applications like nano and vim, or trying to move up and
down in ncurses type menus.

Perhaps it was here, a long while ago that somewhat of a
discussion had been brought up to give some explanations on why
NVDA and other Windows screenreaders seem to crap out in programs
like the command prompt, why they don't track correctly in menus
there, keep track of a cursor, etc, but I don't remember
everything that was said. I do know though that the size of the
window, shape of the cursor, number of lines in that window and
number of allowed characters per line used to be really important
in getting JFW set up for TeraTerm and then it worked considerably
better.

All the same, thanks for the link to an introduction to bash, as
I'm sure that it will be of help for sure, but I was more asking
how one goes about enabling the bash terminal on 10 or if it came
automatically. hehe :)
It's my luck that it's right in front of my face and I'm just
missing it, but there's still quite a lot that I haven't explored
on 10. haha
Here's hoping our wonderful devs may just put a little sweet sweet
love towards the terminal and get it working as well as NVDA does
on lots of other applications, as having a terminal that's easy to
enable and we can use to ssh into those types of systems, that
would be totally sweet.
Take care.

On 8/20/2016 10:39 AM, Brandon Keith Biggs wrote:
Hello,
So I was able to get the bash client working on my computer.
Pros:
The client works great, it is just like powershell or command prompt.
2. SSH works OK. You can read what happened with the review
cursor, but there is a huge lag when typing (nvda will say the
letter like half a second after you type and it is not 100%).
There is no feedback for up arrow to retype commands and no
feedback when letters are deleted.
Other than that things are really good! Vim could use some
tweaking to be a little easier to use, but it is the best. Nano
doesn't like opening existing files. NVDA doesn't read anything
when you open an already existing file with nano.

Because this is pretty much a commandline, is NVDA able to modify
any of these behaviors?
It would be beyond amazing if there was a text editor that had
the usability of EdSharp on the bash line. Vim could be that, but
I have not seen anything to show me it is faster than editing
with EdSharp. Apparently it is not normal for most people to
never leave their keyboard when they are typing and that is what
Vim allows. But EdSharp has even faster key commands and it is a
lot more user friendly.

Here is a guide on how to get started with the bash prompt:
http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/
<http://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/>

Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>

On Fri, Aug 19, 2016 at 2:14 PM, Jeremy
<<mailto:icu8it2@...>icu8it2@...> wrote:

If it's the same thing that was mentioned a while ago here on
list, it does work, but seems to have some of the same issues
in navigating things like ncurses menus and areas such as
files within nano. As with Teraterm and I assume, putty, NVDA
doesn't always track the cursor correctly, so you have to use
review commands to get an idea of your position sometimes.
I'm not sure if this is mostly specific to recent versions of
NVDA, as I know older versions worked really well with
Teraterm, but I do know the latest one can be really
frustrating to use with it.

How does one go about getting and using this bash console in
10, btw, as I'd certainly be willing to give it a shot. Is it
something that comes in the latest anniversary update?
Take care.

On 8/19/2016 3:18 PM, Brandon Keith Biggs wrote:
Hello,
Has anyone managed to give the new windows bash client a try
yet? I am waiting for my update to install. It is a very
functional Ubuntu type system and that means that SSH should
work.
If that is the case, no more needing to deal with partly
accessible SSH clients, we will be able to use the default
windows client!
Thanks,

Brandon Keith Biggs <http://brandonkeithbiggs.com/>