mherrmann / mherrmann/fman

incorrect handling of keys on French keyboard (Windows)

Open
#559 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug windows
Dominant language
Python
Stars
275
Forks
16
PR merge metrics
No merged PRs in 30d

Description

I have a French keyboard, so the numbers on the top row are in shift position:
https://en.wikipedia.org/wiki/AZERTY

For instance, "2" is shifted, and unshifted, it gives "é".

  1. I tried to bind a command to "ctrl+é", but it does not work. I tried also "shift+é", or "shift+ctrl+é": no result. But "shift+2" works, as well as "shift+ctrl+2", while "ctrl+2" does not work. I tried this in Qt (using QShortcut and QKeySequence), and it works correctly: "ctrl+é", "shift+é", "shift+ctrl+é" are all recognized, while "ctrl+2" is not, and neither is "shift+2" (which are impossible key sequences for me). So I think it's a bug on fman's side?

  2. I have assigned some keys frequently used for programming. For instance, when I press "ctrl+=", I get "#", "ctrl+$" gives "}", etc. This is done at the Windows keyboard driver level (MSKLC), and works fine almost everywhere. But when I press "ctrl+=" in fman, nothing happens, while it should start a search for files containing "#" (but "alt+=" for instance, is not "hijacked", so it should be detected by fman, and actually it is).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by reproducing the shortcuts on Windows with a French keyboard layout, comparing fman's handling with the Qt behavior described in the report. Done means the reported combinations, including ctrl+é and ctrl+=, are recognized according to the expected characters and modifier state.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.