Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Invisible text after opening Windows Terminal by double-clicking .bat file #18259

Open
n0samu opened this issue Nov 28, 2024 · 1 comment
Open
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@n0samu
Copy link

n0samu commented Nov 28, 2024

Windows Terminal version

1.21.3231.0

Windows build number

10.0.19045.5131

Other Software

No response

Steps to reproduce

  1. Make sure the Launch Size setting is set to 120 columns and Windows Terminal is set as the default terminal application. Make sure that Windows Terminal opens when you double-click a .bat file.
  2. Create a .bat file with the following code:
@ECHO OFF
CLS & ECHO.
ECHO ------------------------------------------------------------------------------------------------------------------------ 
ECHO.
SET /P INPUT="Enter a filename or URL: "
  1. Close any open terminal windows, then double-click the .bat file to run it.

Expected Behavior

Here's what I see in my terminal window if I run the .bat file from an existing terminal session and type "my input" at the prompt:
Image

Actual Behavior

When I double-click the .bat file to run it in a new terminal window, the prompt text is invisible and the input text appears slightly above where it should:
Image

I have also observed the input text being shifted upward while the prompt text is visible:
Image

@n0samu n0samu added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 28, 2024
@j4james
Copy link
Collaborator

j4james commented Nov 30, 2024

I'm not sure what the problem is, but I think this may be fixed already. I can reproduce it in an old release version of Windows Terminal that I still have installed (v1.20.11781), but not in the preview build (v1.22.2702).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. 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