starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Add settings.json option for turning jumplist population on and off #10732

New Issue
Open
opened 2026-01-31 02:28:51 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:28:51 +00:00
Owner
Copy Link

Originally created by @bavis-m on GitHub (Sep 23, 2020).

Description of the new feature/enhancement

I already use my own custom jumplist editor to put windows terminal profiles (just certain ones) into the jumplist for windows terminal, as well as other software, and other invocations of WT that are more complicated than just loading a profile. It would be nice in this version to be able to turn off the new built-in jumplist creation so my jumplist items don't get overwritten. Plus, I just don't need a jumplist for every profile in addition to the ones I've already manually set up.

Originally created by @bavis-m on GitHub (Sep 23, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I already use my own custom jumplist editor to put windows terminal profiles (just certain ones) into the jumplist for windows terminal, as well as other software, and other invocations of WT that are more complicated than just loading a profile. It would be nice in this version to be able to turn off the new built-in jumplist creation so my jumplist items don't get overwritten. Plus, I just don't need a jumplist for every profile in addition to the ones I've already manually set up. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). -->
claunia added the Issue-TaskProduct-TerminalArea-UserInterface labels 2026-01-31 02:28:51 +00:00
claunia commented 2026-01-31 02:28:52 +00:00
Author
Owner
Copy Link

@dreadnaut commented on GitHub (Sep 23, 2020):

This could be either a global "enableJumplist": false option, or a per-profile "hiddenInJumplist": false setting, which would allow users to customise the jumplist without a 3rd party editor.

@dreadnaut commented on GitHub (Sep 23, 2020): This could be either a global `"enableJumplist": false` option, or a per-profile `"hiddenInJumplist": false` setting, which would allow users to customise the jumplist without a 3rd party editor.
claunia commented 2026-01-31 02:28:52 +00:00
Author
Owner
Copy Link

@bavis-m commented on GitHub (Sep 23, 2020):

As long as "hiddenInJumplist" could go in the "defaults" profile section, and would not cause windows terminal to set an empty jumplist, that would work for me. The problem with that being, if someone had a profile in the jumplist, then at some point hid all their profiles from the jumplist, it would never set the empty jumplist they wanted. That's the reason why I think it would be valuable to have a flag that prevented any jumplist setting (your first option fits the bill there).

@bavis-m commented on GitHub (Sep 23, 2020): As long as "hiddenInJumplist" could go in the "defaults" profile section, and would *not cause windows terminal to set an empty jumplist*, that would work for me. The problem with that being, if someone had a profile in the jumplist, then at some point hid all their profiles from the jumplist, it would never set the empty jumplist they wanted. That's the reason why I think it would be valuable to have a flag that prevented any jumplist setting (your first option fits the bill there).
claunia commented 2026-01-31 02:28:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 23, 2020):

This isn't a terrible idea, but maybe it's something we should combine with #1571, rather than making it a part of each profile. Maybe in the future we'll want the customized new tab menu to appear in the jumplist rather than just the list of profiles.

Though, I suppose most actions won't really make sense from the jumplist, when they might in the new tab dropdown. Plus, I don't think we can do folders in the jumplist.

Maybe I've convinced myself that this should be a part of the profile :P

@zadjii-msft commented on GitHub (Sep 23, 2020): This isn't a terrible idea, but maybe it's something we should combine with #1571, rather than making it a part of each profile. Maybe in the future we'll want the customized new tab menu to appear in the jumplist rather than just the list of profiles. Though, I suppose most actions won't really make sense from the jumplist, when they might in the new tab dropdown. Plus, I don't think we can do folders in the jumplist. Maybe I've convinced myself that this _should_ be a part of the profile :P
claunia commented 2026-01-31 02:28:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 25, 2020):

I'll keep this one open as a discussion. I think we need to land on a design first. 😄

@DHowett commented on GitHub (Sep 25, 2020): I'll keep this one open as a discussion. I think we need to land on a design first. :smile:
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-UserInterface Issue-Task Product-Terminal
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#10732
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?