microsoft / microsoft/PowerToys
| character no more available on a French AZERTY keyboard
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
### Microsoft PowerToys version
0.99.1
### Installation method
PowerToys auto-update
### Area(s) with issue?
General
### Steps to reproduce
I type the AltGr + - key combination on my French AZERTY keyboard.
### ✔️ Expected Behavior
I want to type the pipe character "|"
### ❌ Actual Behavior
The PC enter the text extraction mode (usually obtained by typing the Win + Shift + T combination). Without inserting the pipe character, of course.
This normal key combination works too.
I have removed the normal combination. The pipe character always enters this unwanted mode.
I have reset the default combinations. Always no pipe character available.
I quit PowerToys. The pipe character is now normally alive again.
And once PowerToys is relaunched, I can no more insert the pipe character.
I have also deactivated the text extraction mode tool. And, you know what ? Typing pipe again enters the text extraction mode !!!
With Autohotkey v2, I have also tried another key combination to insert the pipe character and, again, I enter the text extraction mode.
So, it's only when PowerToys doesn't run than I can type a pipe.
WTF ?
### Upload Bug Report ZIP-file
_No response_
### Additional Information
_No response_
### Other Software
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with PowerToys 0.99.1 running on a French AZERTY keyboard, then compare AltGr + - with PowerToys exited. Verify that the pipe character is inserted and text extraction does not start; the issue provides no file or test entry point, so the affected utility must first be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100