Replies: 1 comment 2 replies
-
|
A quick 'n dirty workaround that would work with current rofi: echo -en 'f: one foo\nb: two bar\nz: three baz' | rofi -dmenu -matching regex -no-tokenize -auto-select -filter '^'What does 'mostly undocumented' mean? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a list of items. I want to be able to assign a unique key shortcut to each one, so that when rofi is displaying them, I can press a key and it will instantly select the corresponding item without having to press Enter or anything else. Is this possible? I couldn't find a general solution. What I did find:
-matching prefixBut that has several issues:
-no-tokenizebut it turns out that disables tokenization of the input query rather than the options. E.g. runecho 'one foo\ntwo bar\nthree baz' | rofi -dmenu -matching prefix -no-tokenizeand then typeband it will match the second and third options.)-kb-select-NoptionsThese do work but also have issues:
[a-z0-9]and even punctuation, etc.kb-select-Noption just for one menu, which means that for each menu you need:a. The custom script for the menu
b. A wrapper script which calls rofi with the right config.
Suggested solution
If there's not already a way to solve this, I think it would be much easier if rofi supported a mode where shortcuts can be defined within the menu content, e.g.
would automatically bind
f,b, andzto the first, second, and third options respectively. Then pressing one of those hotkeys would instantly select that option and return.Beta Was this translation helpful? Give feedback.
All reactions