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.

Sign up for GitHub

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

Jump to bottom

Attempting to split pane through command palette crashes Windows Terminal when in settings. #13528

Closed
jackborrie opened this issue Jul 18, 2022 · 2 comments
Closed

Attempting to split pane through command palette crashes Windows Terminal when in settings. #13528

jackborrie opened this issue Jul 18, 2022 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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

@jackborrie
Copy link

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19044.1766

Other Software

No response

Steps to reproduce

  1. Open Settings
  2. Open command palette with keyboard shortcut ([ctrl + shift + p] in my case)
  3. Search "split"
  4. Select "Split pane, split: "

Expected Behavior

A new settings to be opened in parallel to the existing settings.
This way I can edit similar settings at the same time.

Actual Behavior

Windows Terminal crashes
@jackborrie jackborrie added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Jul 18, 2022
@ghost ghost 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 Jul 18, 2022
@zadjii-msft
Copy link
Member

Expected Behavior

A new settings to be opened in parallel to the existing settings. This way I can edit similar settings at the same time.

Alas, that's probably not something which will land for quite some time now - we'd have to land #997 first

As far as the crash is concerned, I can't repro this on 1.15 or 1.14. Can you check out one of those builds off our Releases page/? We may have coincidentally fixed this.

@ghost ghost added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jul 18, 2022
@ianjoneill
Copy link
Contributor

I fixed this in #13172 - this is a dupe of #13166

@similar-issues-ai similar-issues-ai bot mentioned this issue Jul 30, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ianjoneill @zadjii-msft @jackborrie