Skip to content

Conversation

@ralfbrown
Copy link
Contributor

Documents darktable-org/darktable#19410 and darktable-org/darktable#19500 plus some previously existing shortcuts for processing modules.

Status set to draft because I want feedback before spending time going through all of the new shortcuts....

@elstoc
Copy link
Contributor

elstoc commented Oct 31, 2025

Hmm I'm not sure about this. Documenting all the default shortcuts feels like a bit of a maintenance nightmare, especially when the "help" key can also be used to show them to the user. I can see this stuff getting out of date really quickly.

We have purposely excluded shortcuts from the manual except for those few that are hardcoded and cannot be changed in preferences.

This leaves only the handfull of processing module shortcuts created
in C code at program startup.
@ralfbrown ralfbrown marked this pull request as ready for review November 2, 2025 15:44

# shortcut keys

c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure whether definition lists really work well for shortcuts. In other places I've used fenced code blocks, but I'm not sure how well those work either TBH. Maybe a bullet list might work? Also, we generally use fixed width for keyboard keys.

@elstoc
Copy link
Contributor

elstoc commented Nov 4, 2025

Documenting all the default shortcuts feels like a bit of a maintenance nightmare

All of the shortcuts in this PR are default shortcuts that can be user-disabled. As I say, I'm not convinced we should document these at all. Or at least if we start it's hard to know where to stop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants