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

Feature Request: Save current config as Initial #1410

New Issue
Closed
opened 2026-01-30 22:25:24 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:25:24 +00:00
Owner
Copy Link

Originally created by @Kryptryx on GitHub (May 29, 2019).

Summary of the new feature/enhancement

An option on the drop-down menu to save the current config as the initial config. In particular, the overall window position and size, and which tabs are open, and the current font size/rows/columns since it may be zoomed in/out.

I move the main window around. I resize it. I do the ctrl-scroll to get the font size where I need it. I open my preferred tabs in the preferred order. Then I want to say 'save this, and start here next time'. Not quite the same as 'restore how it was when I exited' (another fine feature).

I see there is an 'export settings' feature. This would be more of an 'export' followed by immediate import, presumably skipping the exported file.

Originally created by @Kryptryx on GitHub (May 29, 2019). # Summary of the new feature/enhancement An option on the drop-down menu to save the current config as the initial config. In particular, the overall window position and size, and which tabs are open, and the current font size/rows/columns since it may be zoomed in/out. I move the main window around. I resize it. I do the ctrl-scroll to get the font size where I need it. I open my preferred tabs in the preferred order. Then I want to say 'save this, and start here next time'. Not quite the same as 'restore how it was when I exited' (another fine feature). I see there is an 'export settings' feature. This would be more of an 'export' followed by immediate import, presumably skipping the exported file.
claunia commented 2026-01-30 22:25:26 +00:00
Author
Owner
Copy Link

@binarycrusader commented on GitHub (May 30, 2019):

This feels strongly related to #766 and #1043, although as Kryptryx suggested it's not exactly the same.

@binarycrusader commented on GitHub (May 30, 2019): This feels strongly related to #766 and #1043, although as Kryptryx suggested it's not exactly the same.
claunia commented 2026-01-30 22:25:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 27, 2019):

Hey so we discussed this yesterday.

We could maybe add a ShortcutAction that gets the runtime position, opacity, fontSize, etc, and writes them back to the profiles.json in the current state. We'd want to do this very carefully, because as of #2475, we're not in the business of re-serializing the settings, so we'd want to do a careful insertion.

By making it a ShortcutAction, we could pair it with #2046 / #2193.

I'd also want that action to be spec'd before work starts on it. What settings would be persisted? How do we handle global settings vs per-profile settings? There's much to work out here.

In fact, with #1142, we could maybe add an optional arg that specified which parts of the current state you wanted to save (though that might be overkill)

@zadjii-msft commented on GitHub (Aug 27, 2019): Hey so we discussed this yesterday. We could maybe add a `ShortcutAction` that gets the runtime position, opacity, fontSize, etc, and writes them back to the profiles.json in the current state. We'd want to do this _very_ carefully, because as of #2475, we're not in the business of re-serializing the settings, so we'd want to do a careful insertion. By making it a `ShortcutAction`, we could pair it with #2046 / #2193. I'd also want that action to be spec'd before work starts on it. What settings would be persisted? How do we handle global settings vs per-profile settings? There's much to work out here. In fact, with #1142, we could maybe add an optional arg that specified which parts of the current state you wanted to save (though that might be overkill)
claunia commented 2026-01-30 22:25:26 +00:00
Author
Owner
Copy Link

@fishzle commented on GitHub (Mar 11, 2020):

I think there are too many options and not one clear path through this wood.
KISS.

wt must not become a swiss-army knife of terminals. XTerm grew to have a billion options, so people wanted to have something lightweight and simple.

Please stay true to purpose. "a better cmd / console" (or whatever it was when you started).

@fishzle commented on GitHub (Mar 11, 2020): I think there are too many options and not one clear path through this wood. KISS. wt must not become a swiss-army knife of terminals. XTerm grew to have a billion options, so people wanted to have something lightweight and simple. Please stay true to purpose. "a better cmd / console" (or whatever it was when you started).
claunia commented 2026-01-30 22:25:27 +00:00
Author
Owner
Copy Link

@jamietre commented on GitHub (May 12, 2020):

There should be at least a way to restore the open tabs/window split state, and current directories of each terminal. This feature is found on popular terminals for other platforms, e.g. iTerm2 on OSX and Guake on Linux. Since this is a very small amount of data, it could easily just be stored in the config file, allowing users to self manage it.

@jamietre commented on GitHub (May 12, 2020): There should be at least a way to restore the open tabs/window split state, and current directories of each terminal. This feature is found on popular terminals for other platforms, e.g. iTerm2 on OSX and Guake on Linux. Since this is a very small amount of data, it could easily just be stored in the config file, allowing users to self manage it.
claunia commented 2026-01-30 22:25:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 3, 2022):

Looking over this issue again, and I think we may want to just close this out. We've got "firstWindowPreference": "persistedWindowLayout" which pretty much covers this use case. There are additional follow ups in #9800, and might be a good thread for more discussions.

#11526 is gonna track "add support for creating a command that can reopen this specific set of tabs&panes", which is similar to this (if you don't want to just always restore the existing layout).

@zadjii-msft commented on GitHub (Aug 3, 2022): Looking over this issue again, and I think we may want to just close this out. We've got [`"firstWindowPreference": "persistedWindowLayout"`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/startup#behavior-when-starting-a-new-terminal-session) which pretty much covers this use case. There are additional follow ups in #9800, and might be a good thread for more discussions. #11526 is gonna track "add support for creating a command that can reopen this specific set of tabs&panes", which is similar to this (if you don't want to just _always_ restore the existing layout).
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 Area-Settings Issue-Feature Product-Terminal Resolution-Fix-Available
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#1410
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?