starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Per-profile wordCharacters #4288

New Issue
Open
opened 2026-01-30 23:43:03 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:43:03 +00:00
Owner
Copy Link

Originally created by @egmontkob on GitHub (Oct 5, 2019).

Description of the new feature/enhancement

"wordDelimiters" is a global config option rather than a per-profile one, although there's nothing in this option that inherently has to make it a global one.

In gnome-terminal we had quite a lot of debates around which character should be included and which not. The biggest debate was around :. Folks working with URLs or timestamps want colons to be word characters. Folks working with e.g. grep or compiler outputs (such as filename:matching_content or filename:line_number want the colon to be a stop character.

I can easily imagine that some users would prefer to have different profiles with different double click behaviors, depending on the kind of task they're working on.

Could you guys consider moving it to a per-profile option? Although then it's a bit of maintenance burden when someone wants to update the set and has to do for all the profiles. Feel free to close this bug if it was a deliberate choice from you to make it global.

(On a side note, the same question could also be asked for "copyOnSelect" I guess...?? I'm not sure about that, my gut feelings tell me it's better to have an overall consistent experience here, just as you don't want to have different "keybindings" per profile, but again, these are just feelings.)

Originally created by @egmontkob on GitHub (Oct 5, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 "wordDelimiters" is a global config option rather than a per-profile one, although there's nothing in this option that inherently has to make it a global one. In gnome-terminal we had quite a lot of debates around which character should be included and which not. The biggest debate was around `:`. Folks working with URLs or timestamps want colons to be word characters. Folks working with e.g. `grep` or compiler outputs (such as `filename:matching_content` or `filename:line_number` want the colon to be a stop character. I can easily imagine that some users would prefer to have different profiles with different double click behaviors, depending on the kind of task they're working on. Could you guys consider moving it to a per-profile option? Although then it's a bit of maintenance burden when someone wants to update the set and has to do for all the profiles. Feel free to close this bug if it was a deliberate choice from you to make it global. (On a side note, the same question could also be asked for "copyOnSelect" I guess...?? I'm not sure about that, my gut feelings tell me it's better to have an overall consistent experience here, just as you don't want to have different "keybindings" per profile, but again, these are just feelings.)
claunia added the Help WantedArea-SettingsIssue-TaskProduct-Terminal labels 2026-01-30 23:43:03 +00:00
claunia commented 2026-01-30 23:43:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 24, 2019):

I definitely agree that there's nothing that inherently makes this a global setting. It could certainly be a per-profile setting.

Maybe this is something that would be made easier with #2325, so the "global profile defaults" would have the default settings we provide, and then users could update it per-profile if they wanted.

I concur that copyOnSelect could definitely fit into that category of settings as well.

@zadjii-msft commented on GitHub (Oct 24, 2019): I definitely agree that there's nothing that inherently makes this a global setting. It could certainly be a per-profile setting. Maybe this is something that would be made easier with #2325, so the "global profile defaults" would have the default settings we provide, and then users could update it per-profile if they wanted. I concur that `copyOnSelect` could definitely fit into that category of settings as well.
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 Help Wanted 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#4288
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?