Strange WSL behaviour #10210

Closed
opened 2026-01-31 02:15:27 +00:00 by claunia · 3 comments
Owner

Originally created by @lego963 on GitHub (Aug 18, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.388]
Windows Terminal version (if applicable): 1.1.2233.0
WSL 2

Steps to reproduce

Open WSL type yes

Expected behavior

-bash: yes: command not found

Actual behavior

image

Originally created by @lego963 on GitHub (Aug 18, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.388] Windows Terminal version (if applicable): 1.1.2233.0 WSL 2 ``` # Steps to reproduce Open WSL type `yes` # Expected behavior `-bash: yes: command not found` # Actual behavior ![image](https://user-images.githubusercontent.com/17201690/90523982-2ddbee00-e176-11ea-9c7e-4c9115fa14f2.png)
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 02:15:27 +00:00
Author
Owner

@lego963 commented on GitHub (Aug 18, 2020):

Should I open issue in WSL repo?

@lego963 commented on GitHub (Aug 18, 2020): Should I open issue in WSL repo?
Author
Owner

@zadjii-msft commented on GitHub (Aug 18, 2020):

That's absolutely the expected behavior. yes is a utility that's shipped with ubuntu (and I bet it's shipped with most linux distros, as it's part of the GNU coreutils). Why would you expect yes to not exist?

@zadjii-msft commented on GitHub (Aug 18, 2020): That's absolutely the expected behavior. `yes` is a utility that's shipped with ubuntu (and I bet it's shipped with most linux distros, as it's part of the GNU coreutils). Why would you expect `yes` to not exist?
Author
Owner

@lego963 commented on GitHub (Aug 18, 2020):

sorry for my misstake

@lego963 commented on GitHub (Aug 18, 2020): sorry for my misstake
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10210