Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Keyboard shortcuts: support `Ctrl+W` and `Esc` to close sub-windows, and `Ctrl+Q` to quit the app

Open
  • Is something wrong?
#59 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

The issue lists the dialogs to change: Preferences, Columns, Filters, Analyze Blame, Systemd info, List Boots and Watch signals. Start by finding where each of these windows is built and where the app currently handles keyboard shortcuts. Done means Ctrl+W and Esc close each listed sub-window when no search entry or popover has focus, and Ctrl+Q quits the app. Check the three existing comments for any design decisions first.

Written by the indexing model from the issue text.

Description

As of version 2.19.2 (from Flathub) and older, I noticed that these somewhat standard GNOME keyboard shortcuts are not really used by the app:

  • Ctrl+Q to quit the app
  • Ctrl+W to close any window (not just Alt+F4)
  • Esc to dismiss/close dialogs (i.e. sub-windows), when there is no focused SearchEntry widget or active popover widget in those windows etc. For example in:
    • Preferences dialog
    • Columns dialog
    • Filters dialog
    • Dialogs from the hamburger menu:
      • Analyze Blame dialog
      • Systemd info ("Unit properties") dialog
      • List Boots dialog
      • Watch signals dialog
      • …
    • The only exceptions where this currently works are the standard GTK/libadwaita dialogs such as the Keyboard Shortcuts dialog and the About dialog ;)
Dominant language
Rust
Stars
251
Forks
11
Avg merge
7h 14m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from plrigaux/sysd-manager

All issues in plrigaux/sysd-manager

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.