starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

display current initialPosition/initialRows/initialCols #6635

New Issue
Closed
opened 2026-01-31 00:43:32 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:43:32 +00:00
Owner
Copy Link

Originally created by @bruceoberg on GitHub (Feb 26, 2020).

Description of the new feature/enhancement

After the window position and size has been adjusted manually, I'd like to know exactly which numbers to set for initialPosition, initialRows, and initialCols in my profile. That is, I want to adjust my window by hand and then restore to that later.

Proposed technical implementation details (optional)

Hard to say... I just want to see the numbers. Perhaps some text in the about box? Or some commented out text in settings.json so that I can uncomment it to restore the window?

(Note that this is related to #4620 where I want to set the numbers from the command line. I need a way to adjust the window and get the numbers for my command line parameters, if that is ever offered).

Originally created by @bruceoberg on GitHub (Feb 26, 2020). # Description of the new feature/enhancement After the window position and size has been adjusted manually, I'd like to know exactly which numbers to set for `initialPosition`, `initialRows`, and `initialCols` in my profile. That is, I want to adjust my window by hand and then restore to that later. # Proposed technical implementation details (optional) Hard to say... I just want to see the numbers. Perhaps some text in the about box? Or some commented out text in `settings.json` so that I can uncomment it to restore the window? (Note that this is related to #4620 where I want to set the numbers from the command line. I need a way to adjust the window and get the numbers for my command line parameters, if that is ever offered).
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:43:32 +00:00
claunia commented 2026-01-31 00:43:33 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 10, 2020):

Sorry for taking so long -- I've been deliberating about what the best thing to do with this feature request is. First off: thanks for filing it! I think it's worthwhile.

I feel like this is something we're going to tackle more holistically with the status bar (#3459), which could display things like the current window/pane size, and a floating drag indicator that shows where the window is/how big it is while you're moving it around. I'd prefer to use those as more natural affordances than finding somewhere in the UI to stick ephemeral data like this.

I toyed with a couple other ideas:

  1. a way to copy a JSON blob for the active configuration
  2. A way to commit the active settings as default (#1056)

At the end of the day, though, this'll be helped immensely by the settings UI (#1564) ... so I'm going to close it out.

In favor of one of those three bugs: this is either behavior that would be encompassed by, or a /dupe of #1056 #3459 and #1564.

Thanks!

@DHowett-MSFT commented on GitHub (Apr 10, 2020): Sorry for taking so long -- I've been deliberating about what the best thing to do with this feature request is. First off: thanks for filing it! I think it's worthwhile. I feel like this is something we're going to tackle more holistically with the status bar (#3459), which could display things like the current window/pane size, and a floating drag indicator that shows where the window is/how big it is while you're moving it around. I'd prefer to use those as more natural affordances than finding somewhere in the UI to stick ephemeral data like this. I toyed with a couple other ideas: 1. a way to copy a JSON blob for the active configuration 2. A way to commit the active settings as default (#1056) At the end of the day, though, this'll be helped immensely by the settings UI (#1564) ... so I'm going to close it out. In favor of one of those three bugs: this is either behavior that would be encompassed by, or a /dupe of #1056 #3459 and #1564. Thanks!
claunia commented 2026-01-31 00:43:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 10, 2020):

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 commented on GitHub (Apr 10, 2020): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6635
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?