Feature Request: Dedicated serial port connection settings #1694

@DHowett-MSFT commented on GitHub (Jun 18, 2019):

This will best be handled by some combination of #555 and #626.

@DHowett-MSFT commented on GitHub (Jun 18, 2019): This will best be handled by some combination of #555 and #626.

claunia commented

@DHowett-MSFT commented on GitHub (Jun 18, 2019):

@hassanuz might be interested in this.

@DHowett-MSFT commented on GitHub (Jun 18, 2019): @hassanuz might be interested in this.

claunia commented

@DHowett-MSFT commented on GitHub (Jun 18, 2019):

This is something you can do today with a bit of finagling; we'll be looking at what it means to remember SSH connections. The main point of contention is that we're not a dedicated SSH client like putty and secureCRT are. Perhaps the Terminal isn't the right place for it?

@DHowett-MSFT commented on GitHub (Jun 18, 2019): This is something you can do today with a bit of finagling; we'll be looking at what it means to remember SSH connections. The main point of contention is that we're not _a dedicated SSH client_ like putty and secureCRT are. Perhaps the Terminal isn't the right place for it?

claunia commented

2026-01-30 22:34:00 +00:00

@pilcherd commented on GitHub (Jun 22, 2019):

I would like the ability to have a Serial Port terminal too.

I.e. open with baud rate/COM port settings etc.

I know it feels so 1980's but in some fields there are many people who use it. Putty supports a basic serial terminal so it's not that outside of the norm.

For all terminals, would like to be able to log terminal output to a file in different formats (raw/text) too.

@pilcherd commented on GitHub (Jun 22, 2019): I would like the ability to have a Serial Port terminal too. I.e. open with baud rate/COM port settings etc. I know it feels so 1980's but in some fields there are many people who use it. Putty supports a basic serial terminal so it's not that outside of the norm. For all terminals, would like to be able to log terminal output to a file in different formats (raw/text) too.

claunia commented

@timoline commented on GitHub (Jun 23, 2019):

IMHO, WT would be the perfect place for these kind of connections.
All in one solution

@timoline commented on GitHub (Jun 23, 2019): IMHO, WT would be the perfect place for these kind of connections. All in one solution

claunia commented

2026-01-30 22:34:00 +00:00

@nntantidakis commented on GitHub (Jun 23, 2019):

pilcherd serial port connection is not 1980's. I mainly work with Wemos,Arduino etc and using serial port is extremely common. And the most frustating part of every program that reads serial connection is the fact that if the device disconnects, it closes the reader and they do not keep searching when the device will come online again for it to reopen automatically... So if you implement serial port terminal, please make it in a way that if your terminal detects a disconnection, not to close the tab-window but to inform the user that the device was disconnected,and reconnect automatically when the COM port becomes available again.

Also for logging to text you can use pipes, for example ping 8.8.8.8 > test.txt

You should know that if you also implement the following feature you will attract lots of users that work mainly with esp microcontrollers.

@nntantidakis commented on GitHub (Jun 23, 2019): pilcherd serial port connection is not 1980's. I mainly work with Wemos,Arduino etc and using serial port is extremely common. And the most frustating part of every program that reads serial connection is the fact that if the device disconnects, it closes the reader and they do not keep searching when the device will come online again for it to reopen automatically... So if you implement serial port terminal, please make it in a way that if your terminal detects a disconnection, not to close the tab-window but to inform the user that the device was disconnected,and reconnect automatically when the COM port becomes available again. Also for logging to text you can use pipes, for example ping 8.8.8.8 > test.txt You should know that if you also implement the following feature you will attract lots of users that work mainly with esp microcontrollers.

claunia commented

2026-01-30 22:34:00 +00:00

@pilcherd commented on GitHub (Jun 24, 2019):

@nntantidakis I use serial ports in embedded device and instrumentation development daily. My point was not that people don't use it today, but rather than most people will undervalue the importance of it for a select industries. For most it feels an old or little used technology, but in the age of IoT it's growing in demand again.

@pilcherd commented on GitHub (Jun 24, 2019): @nntantidakis I use serial ports in embedded device and instrumentation development daily. My point was not that people don't use it today, but rather than most people will undervalue the importance of it for a select industries. For most it feels an old or little used technology, but in the age of IoT it's growing in demand again.

claunia commented

@YaSuenag commented on GitHub (Aug 5, 2019):

I hope that Windows Terminal provides features for serial console and SSH connection too. I think it is enough just a wrapper for them.

So I push them to my repository. They are very simple. I hope Windows Terminal will have similar features in the future.

Serial console: https://github.com/YaSuenag/SimpleCom
SSH client: https://github.com/YaSuenag/ssh-ps-wrapper

@YaSuenag commented on GitHub (Aug 5, 2019): I hope that Windows Terminal provides features for serial console and SSH connection too. I think it is enough just a wrapper for them. So I push them to my repository. They are very simple. I hope Windows Terminal will have similar features in the future. * Serial console: https://github.com/YaSuenag/SimpleCom * SSH client: https://github.com/YaSuenag/ssh-ps-wrapper

claunia commented

@rbharathkumar commented on GitHub (Jul 4, 2020):

Considering the number of requests seen in the GitHub issues, I think the demand for Windows Terminal to come with its own ssh client is quite high, it would be really wonderful to include it. I believe the usage would skyrocket and bring in better feedback and request for features. I myself was looking to raise a similar issue but then saw the numerous others...
Thanks for all the hard work on the Windows Terminal.

@rbharathkumar commented on GitHub (Jul 4, 2020): Considering the number of requests seen in the GitHub issues, I think the demand for Windows Terminal to come with its own ssh client is quite high, it would be really wonderful to include it. I believe the usage would skyrocket and bring in better feedback and request for features. I myself was looking to raise a similar issue but then saw the numerous others... Thanks for all the hard work on the Windows Terminal.

claunia commented

@DHowett commented on GitHub (Jul 4, 2020):

At least for now, Windows comes with a well-known and verifiable SSH client. Us relying on the one that comes with Windows means you don’t need to trust Terminal to be a security broker 😄

For now, that’s a better position for everyone to be in.

@DHowett commented on GitHub (Jul 4, 2020): At least for now, *Windows* comes with a well-known and verifiable SSH client. Us relying on the one that comes with Windows means you don’t need to trust Terminal to be a security broker 😄 For now, that’s a better position for everyone to be in.

claunia commented

@samerhaj commented on GitHub (Jul 4, 2020):

What about serial console manager? This issue seems to be tracking multiple requests. For me, a serial console manager would be an excellent addition to Windows Terminal, and removes the need to use additional programs just for serial connections to boards/devices.

@samerhaj commented on GitHub (Jul 4, 2020): What about serial console manager? This issue seems to be tracking multiple requests. For me, a serial console manager would be an excellent addition to Windows Terminal, and removes the need to use additional programs just for serial connections to boards/devices.

claunia commented

@rbharathkumar commented on GitHub (Jul 6, 2020):

At least for now, Windows comes with a well-known and verifiable SSH client. Us relying on the one that comes with Windows means you don’t need to trust Terminal to be a security broker 😄

For now, that’s a better position for everyone to be in.

Thank you for your response. I totally agree with you...One less thing to maintain and good part is that it is something we can rely and trust on...But there are some points to note though...

The OpenSSH Client that comes with Windows needs to be enabled from the Optional Windows Features meaning that if we do not have admin right which most corporate PCs and Laptops do not, we will not be able to enable it.
The OpenSSH Client option does not show up in some PCs like mine, I am currently on 1909 fully updated to date, I see the OpenSSH Server option but not the Client. I googled and found few other people having the same issue. (Not at all related to the Windows Terminal...but just FYI)
The installation instructions from the OpenSSH Portable github page seems a little complex with all its dependencies including a compiler and so on. Would be truly easier if Terminal came bundled with it or atleast enabled it via an option ?

I totally understand the logic behind the decision and Windows Terminal is not exactly geared towards that use case or the right tool for an SSH Client, but would be nice to have though..

Thank you once again.

@rbharathkumar commented on GitHub (Jul 6, 2020): > > > At least for now, _Windows_ comes with a well-known and verifiable SSH client. Us relying on the one that comes with Windows means you don’t need to trust Terminal to be a security broker 😄 > > For now, that’s a better position for everyone to be in. Thank you for your response. I totally agree with you...One less thing to maintain and good part is that it is something we can rely and trust on...But there are some points to note though... 1. The OpenSSH Client that comes with Windows needs to be enabled from the Optional Windows Features meaning that if we do not have admin right which most corporate PCs and Laptops do not, we will not be able to enable it. 2. The OpenSSH Client option does not show up in some PCs like mine, I am currently on 1909 fully updated to date, I see the OpenSSH Server option but not the Client. I googled and found few other people having the same issue. (Not at all related to the Windows Terminal...but just FYI) 3. The installation instructions from the OpenSSH Portable github page seems a little complex with all its dependencies including a compiler and so on. Would be truly easier if Terminal came bundled with it or atleast enabled it via an option ? I totally understand the logic behind the decision and Windows Terminal is not exactly geared towards that use case or the right tool for an SSH Client, but would be nice to have though.. Thank you once again.

claunia commented

@GitSheru commented on GitHub (Nov 1, 2021):

I would like the ability to have a Serial Port terminal too.

I.e. open with baud rate/COM port settings etc.

I know it feels so 1980's but in some fields there are many people who use it. Putty supports a basic serial terminal so it's not that outside of the norm.

For all terminals, would like to be able to log terminal output to a file in different formats (raw/text) too.

This should be a separate feature request. Much needed features

@GitSheru commented on GitHub (Nov 1, 2021): > I would like the ability to have a Serial Port terminal too. > > I.e. open with baud rate/COM port settings etc. > > I know it feels so 1980's but in some fields there are many people who use it. Putty supports a basic serial terminal so it's not that outside of the norm. > > For all terminals, would like to be able to log terminal output to a file in different formats (raw/text) too. This should be a separate feature request. Much needed features

claunia commented

@GanterFengDavid commented on GitHub (Apr 23, 2024):

3 years passed. Any progress on this feature request?

@GanterFengDavid commented on GitHub (Apr 23, 2024): 3 years passed. Any progress on this feature request?

claunia commented