20
849
Fork
You've already forked fuzzel
83

Set key bindings via parameter #759

Closed
opened 2026年05月07日 21:47:58 +02:00 by fdw · 0 comments

Pre-checks

Do similar tools already implement this feature?

rofi does

Describe your feature request

I'm the author of rofi-rbw, which supports many dmenu-style launchers. With rofi, it's possible to pass custom key bindings to the launcher that make sense for rofi-rbw.

Currently, fuzzel can do custom key bindings, but they are only configurable via the config file. But I neither want the user to define sensible key bindings globally, nor do I want to automatically create a config file for them. It'd be perfect if I could pass key bindings via parameters for just this one call.

### Pre-checks - [x] The [fuzzel.ini](https://codeberg.org/dnkl/fuzzel/src/branch/master/doc/fuzzel.ini.5.scd) and [fuzzel](https://codeberg.org/dnkl/fuzzel/src/branch/master/doc/fuzzel.1.scd) man pages. - [x] [Changelog](https://codeberg.org/dnkl/fuzzel/src/branch/master/CHANGELOG.md#unreleased) of newer and unreleased features ### Do similar tools already implement this feature? `rofi` does ### Describe your feature request I'm the author of [rofi-rbw](https://github.com/fdw/rofi-rbw), which supports many dmenu-style launchers. With `rofi`, it's possible to pass custom key bindings to the launcher that make sense for `rofi-rbw`. Currently, `fuzzel` can do custom key bindings, but they are only configurable via the config file. But I neither want the user to define sensible key bindings globally, nor do I want to automatically create a config file for them. It'd be perfect if I could pass key bindings via parameters for just this one call.
Sign in to join this conversation.
No Branch/Tag specified
master
gnome-support
releases/1.14
issue-319-window-switching
issue-561-nord-theme-only
resvg-filtering-take-2
resvg-filtering
releases/1.13
rehanzo-dont-ignore-execute-648
keybinds-overwrite
issue-561-refresh-theme
ci-automated-testing
reenable-legacy-icons
releases/1.12
test-coverage-for-fzf-caching
releases/1.11
releases/1.10
releases/1.9
releases/1.8
releases/1.7
releases/1.6
releases/1.5
releases/1.4
releases/1.3
releases/1.2
releases/1.1
releases/1.0
1.14.1
1.14.0
1.13.1
1.13.0
1.12.0
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.2
1.8.1
1.8.0
1.7.0
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.2
1.4.1
1.4.0
1.3.0
1.2.0
1.1.0
1.0.1
1.0.0
0.9.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/fuzzel#759
Reference in a new issue
dnkl/fuzzel
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?