You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: to add a keyboard-first, searchable code picker for selected text. #1493
Is your feature request related to a problem? Please describe.
The current Recent Codes is useful:
User selects text
User presses R
User can use arrow keys to focus on code, then press enter to select
However, it is limited to recently used codes. In projects with larger codebooks, it would useful to have a feature that can search and apply codes without moving to the mouse, hovering over the sidebar, scrolling, and then returning to the keyboard. For keyboard-first users, this would save a lot of time to have a feature with similar behavior to Recent Codes.
Describe the solution you'd like
The proposed workflow could look like this:
User selects text
User presses F
User types part of a code, a search box populates with code names, user focuses on populated terms with arrow keys, then presses enter to input code
I envisioned this like Zotero's citation picker functionality (or, similar to searching for something in Finder, or command palettes in various apps).
In the Code Text editor view, user selects text, then presses F
A new dialogue box appears, with a search text field, which is in focus automatically
In the same dialogue box, underneath the search search text field, is a box in which all codes are displayed
The code box is filtered live as a user types in the search text field, searching for their intended code
Up/down arrows change the highlighted returned code, while typing focus remains in the search text field
Enter applies the highlighted code to the text, and also closes the dialogue box
Escape cancels the dialogue box
Describe alternatives you've considered
I realized after completing an initial local prototype (I was excited to play around with Python), that the contributor guidelines ask contributors to discuss an issue and wait for assignment before opening a pull request. I do not want to get ahead of the projects process, so I am opening this issue first and will not submit a PR unless the feature is welcome and/or assigned.
I have a locally-tested implementation on a separate branch. It was tested on macOS Tahoe 26.5.2, running QualCoder from source.
Additional context
Add any other context or screenshots about the feature request here.
Hello, thank you for your idea. It sounds good. Currently, we are wrapping up the 4.0-beta release and will not be adding any new features just yet. But this can be implemented in the subsequent code base.
Our timeline is to release the 4.0-beta probably in 1 week's time, have the beta release available for 6 weeks to collect feedback/errors in particular. Then release the final 4.0. Once this release is out, then we can work on and accept PRs for the subsequent version.
Activity
ccbogel commentedon Aug 17, 2026
Hello, thank you for your idea. It sounds good. Currently, we are wrapping up the 4.0-beta release and will not be adding any new features just yet. But this can be implemented in the subsequent code base.
Our timeline is to release the 4.0-beta probably in 1 week's time, have the beta release available for 6 weeks to collect feedback/errors in particular. Then release the final 4.0. Once this release is out, then we can work on and accept PRs for the subsequent version.
qwertygc commentedon Aug 18, 2026
Maybe you can create a draft PR, and we can review and enhance for the 4.1 if you want?
willowsipling commentedon Aug 18, 2026
@ccbogel - how exciting! I'll be looking forward to seeing the new version!
@qwertygc - I will do that (probably later today? or perhaps tomorrow!), and please feel free to look at/implement/or not implement.
Thank you all for the hard work on this amazing software.
Salomon-Mazatlan commentedon Aug 18, 2026
I think it is an excellent idea. It could also be implemented from the context menu, below (or above) "Mark with recent codes".
I have tried it out a little and it makes searching for codes in very long lists much easier, without having to go to the filters in the code tree.
willowsipling commentedon Aug 21, 2026
qwertygc - Thank you for the suggestion, I've sent the draft pull request.
alomon-Mazatlan - glad to see it is useful! This feature, of course, will require localization/translation.