hyprcosmic

290 Commits 4 Branches 42 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
gitops	fc8c2a727d	waybar: six more modules, and a keyboard reference the session had none of The bar showed which windows existed but not which one had the keyboard, and nothing at all about the GPU, the fans, the disk, or a unit that had failed at boot. Six modules, two of which needed a script because waybar has no module that fits. hyprland/window, and no compositor change Reading the active window needs `j/activewindow` on startup and `activewindow>>` on .socket2.sock, and hypr_ipc already serves both. A retitle of the focused window propagates too, which is the case that usually needs a separate `windowtitle` event: this fork diffs a snapshot on a 150 ms tick rather than emitting from call sites, so src/hypr_ipc/ sync.rs sees a (class, title) change and cannot miss it. There is already a test for exactly that -- title_change_alone_emits_activewindow. The rewrite rules trim the app suffix from titles written for a title bar rather than a 60-column slot. All five now use the same [-<em dash>] class. Vivaldi had a bare hyphen because it was written from the live title -- j/clients reports "Inbox - ... - Gmail - Vivaldi" -- and the others got the class in a later pass, which left the one rule that would break if Vivaldi ever switched separators. COSMIC's own applications use an em dash and not a hyphen, so a rule written with a hyphen matches nothing there. custom/fan, because neither of the obvious options can name this sensor waybar has no fan module. Its temperature module cannot be borrowed: it divides by 1000 to turn millidegrees into degrees, which renders 2700 rpm as 2 C. Nor can hwmon-path-abs point at the fans. That option names a parent directory and takes the one hwmonN inside it, which works for k10temp and amdgpu because each has exactly one, but asus-nb-wmi has two: hwmon9 name=asus fan1_input, fan2_input hwmon10 name=asus_custom_fan_curve the curve's set points Which of the two waybar picked would be down to readdir order. So the script resolves by content instead -- any hwmon with a fan*_input -- which also makes it work on hardware that is not this laptop. It prints nothing where there is no readable fan, and waybar draws an empty custom module as nothing, so a VM loses the item rather than showing a dead 0 rpm. hyprcosmic-keybinds, and why it does not read cosmic.conf The obvious implementation reads cosmic.conf and would be wrong. This machine's cosmic.conf declares six bindings. The session answers to 122. The other 116 are COSMIC's defaults, which the fork does not restate because it has no reason to -- Super+Q closes a window whether or not anybody wrote it down. A reference showing six entries would not look broken, it would look complete, while missing every window, workspace and media key on the machine. So it reads the three RON files the compositor reads: Shortcuts/v1/ defaults for the built-ins, the user's Shortcuts/v1/custom for what cosmic-conf projected out of cosmic.conf, and Shortcuts/v1/system_actions to turn System(Screenshot) into cosmic-screenshot. Without the third, a third of the list would name internal actions rather than the programs they launch, which is the half of the question that was being asked. Parsing RON with sed deserves a defence. The principled home for this is a `cosmic-conf binds` subcommand, which already has the schema and the bind grammar -- and is a compiled change and a full package build. The files are one binding per line and nothing downstream consumes this, so the cost of being wrong is a mangled row in a help window, not a broken keybinding. The script refuses to show a list it could not parse rather than showing a short one. The binding for it was chosen with the script: Super+K and Super+I are both focus actions in COSMIC's defaults, and Super+Shift+/ is free. install-assets: prune dot-directories from the audit audit_config_tree refuses to run unless every file under config/ is classified, and it started failing on six gitignored .omc/ state files that tooling had dropped into config/waybar/. Failing on those trains you to ignore the one message that catches a genuinely unclassified asset. Dot files are still walked; only directories are pruned. Verified before committing The generated config parses as JSON with all 23 modules defined and none defined but unplaced. The three stylesheets concatenate and parse clean through GTK's own CssProvider, which is the parser waybar uses, and every @colour they name is defined. Both scripts pass a syntax check, and hyprcosmic-keybinds was run with rofi stubbed -- nothing appeared on the desktop -- producing 118 rows, which is 116 defaults plus 6 ours less the 4 that override. System() actions resolved to real commands, chords sorted Super first, and the modifier-only Super binding survived, which a parser requiring a key field would have dropped. Every sensor was read before being wired to a module rather than after: amdgpu edge 55 C, cpu_fan 2700 and gpu_fan 2500 rpm, zero failed units in both scopes, / at 3 percent. Not verified: how any of it looks. Rendering needs waybar restarted against a session that is not at the lock screen.	2026-08-11 07:46:29 +07:00
gitops	08028e6f2c	Add a power menu, so a session can be left without rebooting The hyprcosmic profile disables cosmic-panel, and COSMIC's power applet lives in that panel. Nothing replaced it, so the session had no logout, reboot or shutdown anywhere in it: the only way out was `systemctl reboot` typed into a terminal, which also meant every login-time change cost a reboot to test. hyprcosmic-powermenu is a rofi menu offering lock, suspend, log out, reboot and shut down. It is reached two ways -- $mainMod SHIFT E and a button at the right end of waybar -- and both run the same script, so a click cannot bypass the confirmation a keypress gets. Logging out calls com.system76.CosmicSession.Exit, which is the method the panel applet used and the only one that stops the session's clients in order rather than pulling the compositor out from under them. Reboot and poweroff go straight to systemd; polkit already authorises both for an active local session without a prompt, verified with pkcheck, so no pkexec is involved. Lock uses loginctl, which cosmic-greeter is listening for. Confirmation is asked only for the three that end the session. Lock and suspend undo themselves with a keypress, so a prompt there is pure friction; the other three throw away everything unsaved and are one keystroke away at all times. "No" is listed first so it is the row already selected. The menu entries are plain words rather than Nerd Font glyphs. The bar icon is the only glyph involved, and it comes through generate-config.py, whose whole purpose is that no Private Use Area character is ever typed by hand -- U+F011, confirmed present in the installed JetBrainsMono Nerd Font. rules.css names every module id explicitly, so #custom-power had to be added there too or the button would have rendered with no pill behind it. The script sits under config/bin/ rather than a new top-level directory so that install-assets.sh's audit still covers it: that check refuses to run unless every file under config/ is classified, which is what stops a new file from being silently left uninstalled.	2026-08-10 15:35:45 +07:00

Author

SHA1

Message

Date

gitops

fc8c2a727d

waybar: six more modules, and a keyboard reference the session had none of

The bar showed which windows existed but not which one had the keyboard,
and nothing at all about the GPU, the fans, the disk, or a unit that had
failed at boot. Six modules, two of which needed a script because waybar
has no module that fits.

hyprland/window, and no compositor change

Reading the active window needs `j/activewindow` on startup and
`activewindow>>` on .socket2.sock, and hypr_ipc already serves both. A
retitle of the focused window propagates too, which is the case that
usually needs a separate `windowtitle` event: this fork diffs a snapshot
on a 150 ms tick rather than emitting from call sites, so src/hypr_ipc/
sync.rs sees a (class, title) change and cannot miss it. There is already
a test for exactly that -- title_change_alone_emits_activewindow.

The rewrite rules trim the app suffix from titles written for a title bar
rather than a 60-column slot. All five now use the same [-<em dash>]
class. Vivaldi had a bare hyphen because it was written from the live
title -- j/clients reports "Inbox - ... - Gmail - Vivaldi" -- and the
others got the class in a later pass, which left the one rule that would
break if Vivaldi ever switched separators. COSMIC's own applications use
an em dash and not a hyphen, so a rule written with a hyphen matches
nothing there.

custom/fan, because neither of the obvious options can name this sensor

waybar has no fan module. Its temperature module cannot be borrowed: it
divides by 1000 to turn millidegrees into degrees, which renders 2700 rpm
as 2 C. Nor can hwmon-path-abs point at the fans. That option names a
parent directory and takes the one hwmonN inside it, which works for
k10temp and amdgpu because each has exactly one, but asus-nb-wmi has two:

    hwmon9   name=asus                  fan1_input, fan2_input
    hwmon10  name=asus_custom_fan_curve  the curve's set points

Which of the two waybar picked would be down to readdir order. So the
script resolves by content instead -- any hwmon with a fan*_input -- which
also makes it work on hardware that is not this laptop. It prints nothing
where there is no readable fan, and waybar draws an empty custom module as
nothing, so a VM loses the item rather than showing a dead 0 rpm.

hyprcosmic-keybinds, and why it does not read cosmic.conf

The obvious implementation reads cosmic.conf and would be wrong. This
machine's cosmic.conf declares six bindings. The session answers to 122.
The other 116 are COSMIC's defaults, which the fork does not restate
because it has no reason to -- Super+Q closes a window whether or not
anybody wrote it down. A reference showing six entries would not look
broken, it would look complete, while missing every window, workspace and
media key on the machine.

So it reads the three RON files the compositor reads: Shortcuts/v1/
defaults for the built-ins, the user's Shortcuts/v1/custom for what
cosmic-conf projected out of cosmic.conf, and Shortcuts/v1/system_actions
to turn System(Screenshot) into cosmic-screenshot. Without the third, a
third of the list would name internal actions rather than the programs
they launch, which is the half of the question that was being asked.

Parsing RON with sed deserves a defence. The principled home for this is a
`cosmic-conf binds` subcommand, which already has the schema and the bind
grammar -- and is a compiled change and a full package build. The files
are one binding per line and nothing downstream consumes this, so the cost
of being wrong is a mangled row in a help window, not a broken keybinding.
The script refuses to show a list it could not parse rather than showing a
short one.

The binding for it was chosen with the script: Super+K and Super+I are
both focus actions in COSMIC's defaults, and Super+Shift+/ is free.

install-assets: prune dot-directories from the audit

audit_config_tree refuses to run unless every file under config/ is
classified, and it started failing on six gitignored .omc/ state files
that tooling had dropped into config/waybar/. Failing on those trains you
to ignore the one message that catches a genuinely unclassified asset.
Dot files are still walked; only directories are pruned.

Verified before committing

The generated config parses as JSON with all 23 modules defined and none
defined but unplaced. The three stylesheets concatenate and parse clean
through GTK's own CssProvider, which is the parser waybar uses, and every
@colour they name is defined. Both scripts pass a syntax check, and
hyprcosmic-keybinds was run with rofi stubbed -- nothing appeared on the
desktop -- producing 118 rows, which is 116 defaults plus 6 ours less the
4 that override. System() actions resolved to real commands, chords sorted
Super first, and the modifier-only Super binding survived, which a parser
requiring a key field would have dropped.

Every sensor was read before being wired to a module rather than after:
amdgpu edge 55 C, cpu_fan 2700 and gpu_fan 2500 rpm, zero failed units in
both scopes, / at 3 percent.

Not verified: how any of it looks. Rendering needs waybar restarted
against a session that is not at the lock screen.

2026-08-11 07:46:29 +07:00

gitops

08028e6f2c

Add a power menu, so a session can be left without rebooting

The hyprcosmic profile disables cosmic-panel, and COSMIC's power applet lives
in that panel. Nothing replaced it, so the session had no logout, reboot or
shutdown anywhere in it: the only way out was `systemctl reboot` typed into a
terminal, which also meant every login-time change cost a reboot to test.

hyprcosmic-powermenu is a rofi menu offering lock, suspend, log out, reboot and
shut down. It is reached two ways -- $mainMod SHIFT E and a button at the right
end of waybar -- and both run the same script, so a click cannot bypass the
confirmation a keypress gets.

Logging out calls com.system76.CosmicSession.Exit, which is the method the
panel applet used and the only one that stops the session's clients in order
rather than pulling the compositor out from under them. Reboot and poweroff go
straight to systemd; polkit already authorises both for an active local session
without a prompt, verified with pkcheck, so no pkexec is involved. Lock uses
loginctl, which cosmic-greeter is listening for.

Confirmation is asked only for the three that end the session. Lock and suspend
undo themselves with a keypress, so a prompt there is pure friction; the other
three throw away everything unsaved and are one keystroke away at all times.
"No" is listed first so it is the row already selected.

The menu entries are plain words rather than Nerd Font glyphs. The bar icon is
the only glyph involved, and it comes through generate-config.py, whose whole
purpose is that no Private Use Area character is ever typed by hand -- U+F011,
confirmed present in the installed JetBrainsMono Nerd Font.

rules.css names every module id explicitly, so #custom-power had to be added
there too or the button would have rendered with no pill behind it.

The script sits under config/bin/ rather than a new top-level directory so that
install-assets.sh's audit still covers it: that check refuses to run unless
every file under config/ is classified, which is what stops a new file from
being silently left uninstalled.

2026-08-10 15:35:45 +07:00