Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Full Duplex Operation #18319

Closed
CannibalVox opened this issue Dec 12, 2024 · 3 comments
Closed

Full Duplex Operation #18319

CannibalVox opened this issue Dec 12, 2024 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@CannibalVox
Copy link

Description of the new feature

In #18265 @carlos-zamora informed me that while operating the terminal as full duplex (reading from stdin and writing to stdout at the same time) does work in the stable version of Windows Terminal, Microsoft did not recommend doing so, so a bug with full duplex operation was not actually a bug.

Given that the last half-duplex terminal to exist was decommissioned sometime in the 1990s, however, I suggest that Microsoft undergo a project to add full duplex operation to Windows Terminal. And bring it into line with similar products. While Carlos did not believe there were any known use cases for a full duplex terminal, I'm inclined to disagree. While I can't speak for anyone else, the Go programming language does not have the capability to cancel reading from stdin, meaning that no application written in Go is capable of half-duplex operations. I believe that adding Full Duplex capability to Windows Terminal would be a major boon for Go developers, especially since we all thought Windows Terminal already had it.

Proposed technical implementation details

I'm not clear on the technical specifics, but probably do whatever the current version of Windows Terminal does, since Full Duplex works in that version.

@CannibalVox CannibalVox added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 12, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Dec 12, 2024
@DHowett
Copy link
Member

DHowett commented Dec 12, 2024

I'd rather reopen #18265 for discussion than entertain "full duplex operation" as a di novo feature request, if you wouldn't mind. There are a lot of assumptions and messages flying by without response, so please hold up.

@DHowett
Copy link
Member

DHowett commented Dec 12, 2024

In general, turning a legitimate concern (which you do have!) about how your bug report was handled into a somewhat facetious feature request is not conducive to discussion.

@CannibalVox
Copy link
Author

Unfortunately, I don't have a twitter account, so there wasn't really another option.

@microsoft microsoft locked as resolved and limited conversation to collaborators Dec 12, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants