microsoft / microsoft/terminal
`SetConptyOption` API (was: Ctrl-Backspace doesn't respect word delimiters even though normal cmd window does)
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
### Windows Terminal version (or Windows build number)
1.10.2714.0
### Other Software
cmd in a Windows Terminal profile.
### Steps to reproduce
I followed the steps [here](https://github.com/microsoft/terminal/issues/4986) (that is, I set the HKCU\Console\WordDelimiters registry key for cmd). Now if I open a regular cmd window, Ctrl-Backspace respects those word delimiters. But if I do the same in a cmd profile in Windows Terminal, it doesn't respect those delimiters. I've tried making Windows Terminal's word delimiters the same as those in that registry key, restarting Windows Terminal and restarting my machine, but it still doesn't work.
### Expected Behavior
If the cursor is at the end of the following line:
C:\>cd users\foo\bar
and I press Ctrl-Backspace, I expect it to delete just the word "bar".
### Actual Behavior
Instead, it deletes the entire string users\foo\bar. This only happens in a cmd profile in Windows Terminal. In a normal cmd window, it only deletes the word "bar" as I expect.
Contributor guide
Research direction
Start by examining how the cmd profile in Windows Terminal handles Ctrl-Backspace compared with a normal cmd window, using the SetConptyOption API and the HKCU\Console\WordDelimiters behavior described here. The work is complete when the API or related handling lets the cmd profile honor the configured word delimiters, deleting only the final word in the reported example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100