Repository navigation
feat(linux): enable native task multi-selection and keyboard row activation - #33
Merged
Merged
Conversation
This was referenced Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Linux Taskly uses
GTK_SELECTION_NONEfor its task list despite the cross-platform PRODUCT-SPEC requiring row selection, Shift/Ctrl selection, Up/Down navigation, Return to expand and Esc to clear. Double-click editing used a custom gesture instead of the native GTKrow-activatedsignal, so keyboard activation could not work.Change
row-activatedon Return/double click to toggle the inline editor; disable single-click activation so a normal click only selects a row. Remove the competing custom task double-click handler to prevent double toggles. Keep list editing double-click and right-click context menus as before.QA before merging
Scope: This is a focused Linux parity step, not full interaction parity: bulk completion, move, delete and Windows multi-selection remain for follow-up PRs. Do not merge or release until all checks are green.