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
This command should open rofi without errors, but gives the following errors:
rofi-pass uses empty keysims to clear the shortcuts, but these currently cause issues with rofi. A workaround I found is to use a single comma (normally used to specify lists, see man rofi-keys(5)) instead of an empty string, which appears to fix the issue. After this fix rofi-pass works normally.
This does seem to be an issue with rofi itself, so I am unsure if this change should be implemented here. I'll open up an issue over there ASAP edit: davatorium/rofi#1950.
Patch:
diff --git a/rofi-pass b/rofi-pass
index 5dba345..ca16ac2 100755
--- a/rofi-pass+++ b/rofi-pass@@ -454,8 +454,8 @@ mainMenu () {
-kb-custom-18 "${insert_pass}"
-kb-custom-19 "${qrcode}"
)
- args+=( -kb-mode-previous "" # These keyboard shortcut options are needed, because- -kb-mode-next "" # Shift+<Left|Right> are otherwise taken by rofi.+ args+=( -kb-mode-previous "," # These keyboard shortcut options are needed, because+ -kb-mode-next "," # Shift+<Left|Right> are otherwise taken by rofi.
-select "$entry"
-p "> " )
The text was updated successfully, but these errors were encountered:
Rofi 1.7.5 seems to not correctly parse empty keybindings on the command-line:
This command should open rofi without errors, but gives the following errors:

rofi-pass uses empty keysims to clear the shortcuts, but these currently cause issues with rofi. A workaround I found is to use a single comma (normally used to specify lists, see man rofi-keys(5)) instead of an empty string, which appears to fix the issue. After this fix rofi-pass works normally.
This does seem to be an issue with rofi itself, so I am unsure if this change should be implemented here.
I'll open up an issue over there ASAPedit: davatorium/rofi#1950.Patch:
The text was updated successfully, but these errors were encountered: