peterfajdiga / peterfajdiga/karousel

[help needed] Change default keybindings so they don't clash with default KDE keybindings

Open
#125 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.1k
Forks
45
PR merge metrics
No merged PRs in 30d

Description

I'll remove most default keybindings, leaving them to the user to assign.
I want to have default keybindings for moving focus and for moving windows.
I want the default keybindings to not clash with default KDE keybindings, so they work out-of-the-box.
I'd prefer the default keybindings to mirror another window manager's default keybindings.
I'd prefer to use the Meta key as the main modifier, because it's usually not used by applications.

I'll list the options I see along with their problems.

Current defaults
  • Move focus with Meta+W,S,A,D
  • Move windows with Meta+Shift+W,S,A,D

Problems:

  • Many clashes with default KDE keybindings, for example Meta+D for Show Desktop
Arrow keys
  • Move focus with Meta+Up,Down,Left,Right
  • Move windows with Meta+Shift+Up,Down,Left,Right

Problems:

  • Many clashes with default KDE keybindings, for example Meta+Right for Quick Tile Window to the Right
i3-style
  • Move focus with Meta+J,K,L,;
  • Move windows Meta+Shift+J,K,L,;

Problems:

  • The ; key is in different positions on different keyboard layouts
  • Meta+L clashes with KDE's Lock Session
PaperWM-style next/previous
  • Move focus with Meta+. and Meta+,
  • Move windows with Meta+Shift+. and Meta+Shift+,

Problems:

  • Meta+. clashes with KDE's Launch Emoji Selector
Other suggestions

If you have a suggestion that doesn't clash with default KDE keybindings and is based on another window manager's default keybindings or makes particularly good sense, please share it.

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

Start by locating the current default keybinding definitions and comparing them with KDE's default bindings, using the options and conflicts listed in the issue as the initial requirements. Done means an agreed keybinding scheme for focus and window movement that avoids the identified clashes and preserves the stated Meta-key preference.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.