- Blur behind: decoration.blur.special, next to Dim behind
- Margin around: a gaps_out workspace rule for each special workspace,
retired and made again on every apply like the window rules, so a
change lands without a reload
- New workspace: a name, a mark from the ones the bar already has and
apps from Add an app. Its key is an ordinary keybinds.json entry, and
the key editor opens on it as soon as the workspace is made. Deleting
one sends its windows to the workspace you are on
- the keys each row shows are the ones keybinds.json has, found by the
Lua they run, with a button to set one when nothing opens it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Changing a bind means opening modules/binds.lua, knowing Lua, and
knowing which dispatcher to call — and there is nowhere in the shell
that even lists what the keys do.
modules/binds.lua stops holding the binds and becomes a loader:
~/.config/lucid/keybinds.json is the list, one entry per line, and each
one is handed to hl.bind inside a pcall, so a broken entry costs that
bind rather than every bind. An entry is a shell command or a Lua
expression — dispatchers, or a function, with utils/functions and
modules/specials in scope — and "each": "workspace" repeats one entry
across workspaces 1-10. The description goes along, so it shows in
hyprctl binds too. The shipped list is what binds.lua bound before,
entry for entry.
- a missing or unparseable file binds a small emergency set instead
(terminal, close, reload, workspaces and Settings) and says so, so a
typo cannot leave a session with no way back
- every load writes what it applied and what failed to
$XDG_RUNTIME_DIR/lucid-keybinds-status.json, which the page reports,
including binds set elsewhere that the page cannot see
- Settings > Keybinds lists, searches, edits, adds, disables and deletes
binds, flags two binds on the same keys, and reloads Hyprland on save
- SUPER+/ shows the whole sheet over the screen; a click on a row opens
its editor. Recording a combo puts Hyprland into an empty submap for
the moment it takes, so the keys reach the editor instead of firing
what they are bound to
- the installer seeds the list the first time and never touches it again
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>