dunst: the menu takes no typed text, so a typed line never becomes a choice
mesh/merge-gate pass: builds dunst → g14, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer delivery to the same trunk took over its walk
mesh/merge-gate pass: builds dunst → g14, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer delivery to the same trunk took over its walk
Review of hq issue 360: rofi without -no-custom hands typed text to dunst as if chosen.
This commit is contained in:
@@ -63,11 +63,11 @@
|
||||
sticky_history = yes
|
||||
history_length = 20
|
||||
|
||||
# The context menu is rofi, which this module installs. Not `dmenu`, the node-launcher's command in
|
||||
# The context menu is rofi (installed by the rofi module); -no-custom keeps typed text from becoming a choice. Not `dmenu`, the node-launcher's command in
|
||||
# ~/.local/bin: dunst runs in the account's service manager, whose PATH does not hold that
|
||||
# directory (seen on the laptop on 2026-10-10), so the menu never opened. Links open in the
|
||||
# desktop's default browser.
|
||||
dmenu = rofi -dmenu -p dunst
|
||||
dmenu = rofi -dmenu -no-custom -p dunst
|
||||
browser = /usr/bin/xdg-open
|
||||
always_run_script = true
|
||||
|
||||
|
||||
Reference in New Issue
Block a user