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

Terminal with 3 split-pane focuses on random pane #10029

Closed
dc1992 opened this issue May 4, 2021 · 3 comments
Closed

Terminal with 3 split-pane focuses on random pane #10029

dc1992 opened this issue May 4, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@dc1992
Copy link

dc1992 commented May 4, 2021

Windows Terminal version (or Windows build number)

1.8.1092.0

Other Software

No response

Steps to reproduce

  • setup Windows Terminal to have 3 terminal (example: "startupActions": "split-pane -p "cmd2"; split-pane -p "cmd2"")
  • open Windows Terminal: the cursor is blinking on a random pane (example n1)
    cursor1
  • close WIndows Terminal
  • open Windows Terminal again: the cursor is blinking on a random pane (example n3)
    cursor2

Expected Behavior

I expect to see the cursor always in the same pane: the one I chose as default.

Actual Behavior

Whenever I open Windows Terminal, the cursor blinks in a different pane (looks like it's random); this causes the user to start writing in a random pane and force him to manually switch pane.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 4, 2021
@zadjii-msft
Copy link
Member

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #6586 for more discussion.

/dup #6586

@ghost
Copy link

ghost commented May 4, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed May 4, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 4, 2021
@dc1992
Copy link
Author

dc1992 commented May 4, 2021

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #6586 for more discussion.

/dup #6586

It doesn't look like the same problem to me, but maybe it's caused by the same bug.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants