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

Why it does not remember window size position? #14488

Closed
henrypp opened this issue Dec 3, 2022 · 3 comments
Closed

Why it does not remember window size position? #14488

henrypp opened this issue Dec 3, 2022 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@henrypp
Copy link

henrypp commented Dec 3, 2022

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

Open terminal. Resize to new position. Close telegram. Open new telegram.

Expected Behavior

No response

Actual Behavior

Position is default. It is not good.
@henrypp henrypp 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 Dec 3, 2022
@henrypp henrypp changed the title Why it does not remember windows size position? Why it does not remember window size position? Dec 4, 2022
@o-sdn-o
Copy link

o-sdn-o commented Dec 4, 2022

Seems this issue is tracked in #9800 and #12633

@henrypp henrypp closed this as completed Dec 5, 2022
@henrypp henrypp reopened this Dec 5, 2022
@zadjii-msft
Copy link
Member

Yea this sounds exactly like /dup #12633 to me.

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2022
@ghost
Copy link

ghost commented Dec 5, 2022

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 Dec 5, 2022
@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 labels Dec 5, 2022
This issue was 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. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@henrypp @o-sdn-o @zadjii-msft