aboutsummaryrefslogtreecommitdiffstats
path: root/hypr
AgeCommit message (Collapse)AuthorFilesLines
23 hourshypr: dash-workspace rule silent, accent changes no longer show the dashboardHEADmasterDanilo M.1-1/+5
Every accent change brought the conky dashboard up from special:dash. udt-accent rewrites conky.conf in place, which conky reloads, and then runs hyprctl reload, which re-applies window rules to existing windows; either path ends with this rule moving the dashboard to its special workspace, and without silent that also shows the workspace. The exec rule in autostart is silent but only covers the first window. Which of the two paths fires was not settled: rewriting conky.conf by hand kept the same window address, so a conky reload alone may not remap it. silent covers both. Checked with hyprctl eval (accepted) and a reload with no configerrors, and confirmed by eye: the dashboard stays hidden through accent changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 daysdocs: why the dashboard's autostart line looks the way it doesDanilo M.1-1/+11
The reasons lived as comments in hypr-theme's autostart.lua. That file is now edited by the quickshell settings window and carries no comments, so they move here, beside the line they explain: the explicit -c config and the [workspace special:dash silent] prefix, which the window rule cannot replace because hl.window_rule rejects silent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25feat(dashboard): describe the dashboard bindDanilo M.1-1/+1
The quickshell keybind reminder lists hyprctl binds -j, which reports Lua actions as an opaque handle, so a bind shows what it does only through its description. This was the one bind left undescribed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-18docs: mark the dashboard's monitor pin as non-functionalDanilo M.1-4/+16
The workspace rule pinning special:dash to DP-1 does not work: special workspaces ignore a workspace_rule's `monitor` and open on whichever monitor has focus. Verified on 0.56.2; upstream hyprwm/Hyprland#7990 and #5570, both closed in the issues-to-discussions migration rather than fixed. The comment claimed the opposite, which was convincing because the rule does register and `hyprctl workspacerules` reports it enabled. The rule stays, so the intent is recorded and the line is ready if upstream fixes it, and the bind now names the manual step: focus DP-1 first. Also notes that the window stays on DP-3 once opened there, so a later toggle is cropped until it is moved back, the conky surface being a fixed 2560x1080. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-17feat: pin the dashboard's workspace to DP-1Danilo M.1-0/+13
The conky surface is a fixed 2560x1080, because Hyprland's fullscreen rule resizes the window but not the drawing surface, so on the 1920-wide DP-3 the dashboard would be cropped. A workspace rule keeps it on the primary monitor. hl.workspace_rule takes `workspace`, not `match`, and has no `name` field, unlike hl.window_rule. Both were checked against the runtime, which rejects an unknown field with "unknown field '<name>'", and hyprctl workspacerules confirms the rule registers with monitor: DP-1. NOT fully verified: whether it holds when the toggle is pressed while DP-3 has focus. One observation suggested the dashboard still followed focus, but it was taken before the reload had applied the rule, and focus could not afterwards be moved to DP-3 without a window or the pointer on it. Every toggle since the reload has opened on DP-1. Worth confirming after a fresh Hyprland start. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-16docs: fix the toggle syntax and verify the unusual rule keysDanilo M.2-11/+26
Four defects, all found while running Task 8. The documented toggle command does not work on this machine. Under the Lua config `hyprctl dispatch` evaluates its argument as Lua, so the plain `hyprctl dispatch togglespecialworkspace dash` fails with "')' expected near 'dash'"; Hyprland even says so in its error. The working form is `hyprctl dispatch 'hl.dsp.workspace.toggle_special("dash")'`, verified toggling special:dash on and off. Also read the result from `monitors[0].specialWorkspace.name`, since activeworkspace keeps reporting the ordinary workspace underneath. `fullscreen` and `no_focus` appear in no existing rule, so they were checked against the runtime rather than left as caveats: hl.window_rule rejects an unknown field with "unknown field '<name>'", and neither produces that error, so both are accepted. A deliberate bogus key confirmed the check itself works. hl.mainMod is nil in any section other than keybindings.lua, which declares `local mainMod = "SUPER"` and never exports it. The plan hedged about this; it now states the literal to use. Task 8's class check ran `conky -c ./conky.conf`, which is gitignored generated output and absent on a fresh clone, so it now renders the config first. Its `pkill -f` also matched the running script's own command line and killed the shell's process group, returning 144 and swallowing the log it had just been told to read; `pkill -x conky` instead, fixed in Tasks 4 and 6 too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-16feat: add Hyprland placement rules and toggleDanilo M.2-0/+97
A Lua section, not a .conf fragment: the live Hyprland config is hyprland.lua requiring sections/, with rules declared through the hl helper API. Pins conky-dash to its own special:dash workspace, fullscreen, no border, no focus, and binds SUPER+S. Not SUPER+D, which keybindings.lua already binds to the unnamed special workspace, and that workspace already hosts the btop scratchpad. no_focus matters because the dashboard starts with the session: without it, it steals focus at login and can be tabbed to like an app. autostart.lua already launches a bare conky, so the README says to change that line rather than add one, which would run two instances. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>