workbenchdev / workbenchdev/Workbench

Workbench claims wrong shortcut will launch GTK inspector

Open
#174 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

gtk
Dominant language
JavaScript
Stars
844
Forks
91
Avg merge
7h 12m
Merged PRs (30d)
1

Description

The Platform Tools module found in the Library says, at the bottom of its rendered output:

As with most GTK applications, you can use the keyboard shortcut
to open the Inspector and select an object to see what it is made of.

Ctrl+Shift+I

Except... Ctrl+Shift+I doesn't open the inspector. On my Fedora 36 system, at least, a Ctrl+Shift+I in Nautilus (for example) results in a "Select All" being performed in the focused window.

Ctrl+Shift+D launches the GTK Inspector.

Edit: (In fact, Ctrl+Shift+I doesn't even open the inspector in Workbench. Even there, the only working shortcut AFAICT is Ctrl+Shift+D.)

Contributor guide

Open the contributing guide

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

Search the Platform Tools module content for the quoted Ctrl+Shift+I shortcut and read the surrounding rendered output. Verify the working GTK Inspector shortcut in Workbench, update the incorrect documentation, and confirm the rendered module shows the corrected shortcut.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.