Repository navigation
Sync upstream quattro through #17201 - #105
Merged
Merged
Conversation
…om#17117) The dropdown test walks a long list with Down presses and asserts that the selection reaches the last row. Each delegate sets currentIndex on a pointer move. The walk scrolls rows under a stationary pointer, so a row that scrolls under the pointer takes the selection back mid-walk. Two CI runs stopped at 5 and 9 of 11. The test moved the pointer to (500, 600) only in cleanup. That coordinate misses the popup by accident, and it does not run before the long-list walk. Park the pointer at (0, 0) before the walk instead. That point is always inside the window and off the popup. Assert currentIndex after every press instead of a fixed wait(50). A stalled walk then reports the step that stalls. With the pointer left over the list, the old test failed all 9 long-list cases on 12 of 12 runs. The fixed test passed 40 of 40 runs with the pointer over the list, and 80 of 80 runs through test/shell.d/dropdown-test.sh.
…macom#17144) The 250ms motion-rules timings from omacom#16889 felt rushed, and the originals before it a touch slow. This brings back the earlier animations, curves and 87% popin included, with every duration cut by 20%: windows move in 303ms and open in 328ms, layers enter in 320ms, fades take 242ms. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
omarchy-settings skipped its etc-overrides on Apple Silicon, so Mac accounts were created from Arch's stock /etc/skel/.bashrc, which never sources default/bash/rc. omarchy-pkgs#1857 fixes the skel file for new accounts; this migration replaces an existing user's ~/.bashrc with default/bashrc, saving the old one as ~/.bashrc.bak. A bashrc that already loads Omarchy's, or a symlink into a dotfiles repo, is left alone. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
lspci names Wildcat Lake's GPU only "[Intel Graphics]", which the video-acceleration check did not match, so intel-media-driver was never installed and video decoded on the CPU. Match that generic name, and install the driver on existing machines it missed. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…17152) Hyprland 0.57 plays a canberra sound for every xdg-system-bell ring, and foot forwards each BEL there by default. Kitty already has its audio bell off; this does the same for every client at the compositor. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
We already hide the update-news popup; the donation nag still appears after upgrades. Disable it alongside. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Hyprland's cm_auto_hdr defaults to switching an HDR-capable monitor into HDR whenever a window goes fullscreen, which left SDR content looking washed out on the Pro Display XDR. Turn it off; no HDR for now. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Draw first-boot setup with the ISO's traced-icon progress screen
Keep an earlier ~/.bashrc.bak when the Apple Silicon bashrc migration runs
Stop stray worktree shells on shell restart
…macom#17159) * Pick resolution and scale per display in the display panel The display panel gets a Resolution row beneath Scale, and both rows now show one line per enabled display instead of acting on the focused one. Resolutions come from each display's own advertised modes: its native size and the smaller modes of the same shape, smallest to largest. omarchy-hyprland-monitor-resolution sets a display's mode, and it and omarchy-hyprland-monitor-scaling take --monitor NAME. Both save through omarchy-hyprland-monitor-persist, which now writes the mode alongside the scale, so a chosen resolution survives reloads and later scale changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Give each display its own segment in the display panel Each display gets a segment of its own, as each agent does in the agents panel: its name and an on/off switch, then its brightness, scale and resolution. This replaces the display list at the bottom. Brightness is read and set per display. Text size stays one row above the segments, since the shell font, GTK and the terminals each take a single size. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Switch displays by tab and arrange them in the display panel The display panel shows one display at a time, under a tab per display, and opens on the focused one. Its rows sit under the tabs: an on/off switch, brightness, scale and resolution. Text size sits above the tabs, since it applies to every display. A layout map at the bottom draws the displays where they sit. Drag one against another's side to move it there, snapping to that display's start, center or end. h/l moves the open display to the left or right of the others. omarchy-hyprland-monitor-layout applies every position in one eval, and omarchy-hyprland-monitor-persist now saves a position along with the scale and mode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Pick the display from the hero and drop turning displays on and off The hero names the display the panel shows, with a button per display on its right to pick another. It opens on the focused display. That display's brightness, scale and resolution follow the hero, and text size and the layout map come last, since every display shares them. Displays can no longer be turned on and off from the panel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Put text size right under brightness in the display panel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep the monitor layout closed up when a monitor's size changes A scale or resolution change beside other monitors now keeps the monitor's position instead of handing it to Hyprland's auto placement. Every monitor to its right or below it then shifts by however much it grew or shrank, through omarchy-hyprland-monitor-layout --resized, and the positions are saved. A smaller mode no longer leaves a gap beside it, and a larger one no longer overlaps its neighbour. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Even out the display panel's spacing and unbox the display picker Rows of pills take the same room above and below as a slider row, and the layout map is as tall as the arrangement inside a slider-like row, so every section keeps the same rhythm. The picker's display icons no longer sit in boxes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Refuse to save a monitor rule that would break monitors.lua omarchy-hyprland-monitor-persist writes its arguments straight into the Lua that Hyprland loads on every change. It now refuses anything that isn't a plain connector, scale, mode or position, and skips GDK_SCALE when the lowest scale can't be read, instead of writing a broken rule or an empty assignment that leaves the whole config unloadable. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Pad the display panel's pills and map by the slider track's inset A slider's row is as tall as its knob, with the thin track centered in it. Rows of pills and the layout map now take the room around that track rather than half a control gap, and the spacer at the end of the panel goes, so every gap above and below what's drawn is the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep the display panel from scrolling past its content Bringing a row into view added a margin below it even when it was the last row and the panel already fit, which scrolled the content past its end and cut the hero off at the top. The scroll now stops at either end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Separate resolution from scale in the display panel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Drop the layout map's highlight box in the display panel The map no longer sits in a cursor box that lights on hover. When the keyboard is on it, the shown display's outline thickens instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Give the display panel's sections icons and a connected display picker Each section label has an icon beside it: a sun for brightness, letter case for text size, expanding arrows for scale, full-screen corners for resolution and two monitors for layout. The hero's display picker is one segmented control, a frame with a cell per display and the shown one filled, instead of separate buttons. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Revert the display panel's section icons and connected picker This reverts commit 542cfda: the section icons and the segmented display picker didn't land well, so the panel goes back to plain labels and separate picker icons. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep resized monitors' neighbours from piling onto each other Shifting the monitors to the right of and below a resized one at once could push two of them onto each other, as with two screens stacked beside a tall one. A shifted monitor that overlaps another now goes back where it was whenever that spot is free, so the layout keeps a gap rather than an overlap. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Take display brightness from every poll in the display panel The panel skipped a poll whose display list matched the last one, and the list carried brightness, so a level changed elsewhere and changed back could leave the panel showing a stale one for good. Brightness now comes from every poll, and only the rest of the list is compared before rebuilding the picker and layout. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Untangle resize pile-ups a third monitor blocks A shifted monitor that overlapped nothing never went back, so it could block the return of two that overlapped each other, and the overlap was saved. While any overlap remains, any shifted monitor whose old spot is free now goes back, the overlapping ones first. If overlaps still remain, the monitors keep their old places when those are clear. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Give the layout map the display panel's cursor on hover Dropping the map's highlight box also dropped its hover handler, so after using a scale or resolution row, h/l kept walking that row's pills instead of moving the shown display. The pointer on the map takes the shared cursor again, without drawing a box. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Save monitor settings by the physical monitor in a state file The display panel's scale, resolution and layout choices were written into ~/.config/hypr/monitors.lua as rules naming the connector. A dock renames its connectors between plugs, so a rule for DP-1 handed one monitor's mode and position to whatever turned up on that port next, and editing the user's Lua in place could leave the whole config unloadable. omarchy-hyprland-monitor-persist now saves one line per monitor in ~/.local/state/omarchy/monitor-settings, keyed by the identity monitor-workspaces gives it: make, model and serial. The new default/hypr/monitor-settings.lua, loaded from toggles.lua after hypr/monitors.lua, applies them while the config loads and again when a monitor arrives, skipping one already running as saved. It also sets GDK_SCALE from the lowest scale, so monitors.lua is never written, and --keep-gdk goes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep monitor settings under state/omarchy/monitors/ The saved settings move from ~/.local/state/omarchy/monitor-settings to ~/.local/state/omarchy/monitors/settings, a directory of their own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep monitor workspaces and the scaling log under state/omarchy/monitors/ Each monitor's workspace blocks move to monitors/workspaces (with monitors/workspaces-merged beside them) and the scaling log to monitors/scaling, next to monitors/settings. A migration moves the existing files over. Until it runs, monitor-workspaces.lua still reads the old blocks, so a config reload first doesn't cost a monitor its workspaces. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Replay only the saved monitor after each save, and rename its migration A layout moves every monitor in one step, then saves them one at a time, and each save replayed every monitor's saved settings. One not yet saved was pulled back to its old position, then forward again on its own save. A save now replays only its own monitor, which already runs as saved, so it just brings GDK_SCALE up to date. The monitors/ migration takes a fresh timestamp: quattro gained an unrelated migration under the same one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Drop the test for the display panel's removed on/off toggle The panel no longer turns displays on and off, so toggleDisplay and its test go. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Move the merged workspace record with the blocks instead of dropping it The merged record sends an unplugged monitor's workspaces home when it returns, and an update doesn't restart Hyprland, so dropping it lost them for the rest of the session. The migration now moves it like the blocks, and monitor-workspaces.lua reads the old file until then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Leave moving the old workspace files to the migration alone monitor-workspaces.lua no longer reads the old files: the migration moves them, and the old ones win, since anything written under monitors/ before it ran started from nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Drop Setup > Monitors from the Omarchy menu The monitor panel now sets each monitor's scale, resolution and arrangement, so the menu no longer opens monitors.lua for them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Bring the laptop panel back as chosen in the display panel Clamshell recovery took the internal panel's scale and position from monitors.lua, but choices made in the display panel now live in the monitor settings and win over that file. A numeric scale there corrected a panel-chosen one back on every idle-wake, and the panel came back at its old mode and position. Clamshell now reads the saved mode, position and scale first. The connector-to-monitor lookup both need moves into a hidden omarchy-hyprland-monitor-identity. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Shape monitors.lua for what the monitor panel doesn't cover Omarchy's default monitor rule and GDK_SCALE move into default/hypr/monitors.lua, so the shipped hypr/monitors.lua is only commented examples for agents and power users: rotation, modes the panel doesn't offer, keeping a monitor off, matching by description, 10-bit color, VRR, and overriding the default scale or GDK_SCALE. Existing copies keep working: they load after the defaults. The Omarchy agent skill sets scale, resolution and position through the monitor commands, and the manual follows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Let the input-device toggle test's fake Hyprland take event handlers toggles.lua now loads the saved monitor settings, which listen for monitors arriving, so the fake hl the test loads it with needs hl.on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Stop the monitors/ migration when the scaling log copy fails The copy hid every failure behind || true, so a full disk could replace the log with a partial one, delete the original and still mark the migration done. The old log now moves over when there's nothing newer, and otherwise a failed copy stops the migration before anything is replaced or deleted, leaving it pending. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…omacom#17166) * Resize a monitor and move its neighbours in one step A scale or resolution change applied the new size first and moved the neighbours after, so a monitor that grew sat over its neighbour for a moment and Hyprland warned about overlapping monitors. The layout command now takes the new mode and applies it in the same eval as the moves, ordered so no step overlaps: the neighbours moving away first, then the monitor, then the ones closing in. Saving no longer replays a monitor's settings either, which could apply the new size on its own; it only brings GDK_SCALE up to date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Move older monitors.lua files over to the monitor panel's settings An older hypr/monitors.lua still carries Omarchy's monitor defaults and the display panel's scale as connector rules. A migration now runs omarchy-hyprland-monitor-config-upgrade, which turns it into the new template plus whatever else it held: the old defaults go, or become plain lines where they were changed; a one-line connector rule with only a mode, position and scale becomes the saved settings of the monitor behind it, when that monitor is known; every other line is kept below the template. The old file is kept as monitors.lua.bak.<time>. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep an older monitors.lua verbatim below the new template The upgrade read monitors.lua line by line as if it understood Lua, so a block comment's contents became live config, a rule inside a conditional was lifted into saved settings, and a custom scale built from an earlier local lost it. It now keeps the old file exactly as written below the new template and drops only lines Omarchy itself shipped there: its old comments and examples, and its defaults where they're unchanged and nothing else uses them. A file that already opens like the template is left alone. Its tests join monitor-scaling-test.sh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Order a resize's moves along a row so none overlaps Every neighbour moving away shared one place in the eval, so in a row of three the middle screen could move into the far one's spot before it had left. Neighbours moving away now go farthest first, and ones closing in nearest first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Document recovery from broken session environment files * Check UWSM environment syntax with sh * Drop the claim that a .bak suffix does not disable an env.d file UWSM 0.27.0 (upstream commit 4cfc107b, fixing Vladimir-csp/uwsm#226) skips *.bak, *.disabled, *.broken and similar names in env.d, and checks each file with sh -n before sourcing it, skipping one with a syntax error. Errors that only happen at run time, like ${PATH:}, still pass sh -n and still stop the desktop from starting, so the recovery steps stand; moving the file out of env.d works on every version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Read the preloader's journal by identifier, and soften the fatal-error claim journalctl --grep matches only the message, and UWSM's "Env output mark ... not found" line contains neither "uwsm" nor "preloader", so the old filter hid it; -t uwsm_env-preloader shows every line the preloader wrote. Not every run-time error aborts sourcing, since UWSM does not set -e, so only a fatal one is said to block login. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
…macom#15076) * Install and remove Dropbox's libappindicator under its current name Arch renamed libappindicator-gtk3 to libappindicator, which provides and replaces the old name. The installer asked for the old name and left omarchy-pkg-add's post-install check to depend on pacman -Q resolving the provide, which older pacman did not do. The remover never matched it at all, because omarchy-pkg-drop compares exact installed names, so removing Dropbox left libappindicator behind. Fixes omacom#11726 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Leave libappindicator installed when another package needs it Naming it beside the Dropbox packages put it in one pacman -Rns transaction, so a retained package that requires it (network-manager-applet, remmina, rustdesk) made pacman refuse the whole removal and leave Dropbox installed. Drop it separately, and only when nothing directly requires it; optional dependents do not block removal, hence -tt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
* Ignore vendor hotkey keyboard devices * Ignore vendor hotkey layout events --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…m#17169) * Let monitors.lua switch off the monitor panel's saved settings Setting omarchy_monitor_panel_settings = false in hypr/monitors.lua, like the omarchy_default_bindings switch, leaves that file alone in charge of every monitor: the saved panel settings aren't applied on load or when a monitor arrives, GDK_SCALE is left to the file, and clamshell recovery ignores them too. The panel's changes then last only until Hyprland reloads. The template, manual and agent skill say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep a panel-changed scale until reload, and read block comments, in clamshell With the panel's choices switched off, clamshell sync corrected an enabled laptop panel back to monitors.lua's scale every two seconds while docked, undoing a panel change straight away instead of at the next reload as documented. It now leaves an enabled panel's scale alone then, and only brings a panel that's off back at the file's scale. Its comment stripping also only knew block comments ending on the same line, so a switch wrapped in a multi-line --[[ ]] still took effect. It now drops a block comment's lines up to its closing ]]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Inkscape draws its own GTK file chooser rather than asking the portal, so neither the portal rule nor the per-app dialog list in system.lua matches it. Left to Hyprland, the chooser opens at whatever size GTK remembers, which on a fresh install is larger than a 1280x800 screen, with Cancel and Open off the edge, and GTK keeps that size for next time. Fixes omacom#11995 Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Let monitors.lua switch off the monitor panel's saved settings Setting omarchy_monitor_panel_settings = false in hypr/monitors.lua, like the omarchy_default_bindings switch, leaves that file alone in charge of every monitor: the saved panel settings aren't applied on load or when a monitor arrives, GDK_SCALE is left to the file, and clamshell recovery ignores them too. The panel's changes then last only until Hyprland reloads. The template, manual and agent skill say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep a panel-changed scale until reload, and read block comments, in clamshell With the panel's choices switched off, clamshell sync corrected an enabled laptop panel back to monitors.lua's scale every two seconds while docked, undoing a panel change straight away instead of at the next reload as documented. It now leaves an enabled panel's scale alone then, and only brings a panel that's off back at the file's scale. Its comment stripping also only knew block comments ending on the same line, so a switch wrapped in a multi-line --[[ ]] still took effect. It now drops a block comment's lines up to its closing ]]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Add a monitor rotate command and save rotation per monitor New omarchy-hyprland-monitor-rotate [--monitor NAME] 0|90|180|270 turns a monitor a quarter turn at a time. A turn swaps the monitor's width and height in the layout, so it goes through the layout command's resize path: the turn and its neighbours closing up apply in one eval. The rotation is saved with the monitor's other settings as a transform field before the identity, and the settings module, clamshell and persist read lines saved before it as well. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rotate a monitor from the layout map's right-click menu Right-clicking a display in the monitor panel's layout map opens a menu of its quarter turns, Normal, 90°, 180° and 270°, with the current one checked, styled like the dock's menu. Choosing one runs omarchy-hyprland-monitor-rotate for that display. The menu sits over the panel's scrolling content so its edge doesn't clip it; a click elsewhere or Esc closes it, Esc before the panel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Share the dock's menu row with the display panel's rotate menu The rotate menu copied the dock's menu row. Both now use shell/Ui/PopupMenuRow, which emits triggered() and leaves closing the menu to its owner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Show the layout map for a single display, so it can be rotated The rotate menu opens from the layout map, which was hidden with only one display on, leaving a single monitor no way to be rotated from the panel. The map now shows for one display too; dragging it and h/l have nowhere to move it, so they do nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
omarchy-hibernation-available measured swap and looked for the resume hook, but never asked the kernel whether it would take a hibernation request. A machine where hibernation is disabled -- lockdown, nohibernate, secretmem, an active CXL device -- still got the Hibernate menu row, and selecting it ran `systemctl hibernate` detached with its output on /dev/null, so logind's refusal was invisible and the machine simply stayed awake. The kernel lists "disk" in /sys/power/state exactly while it will accept the request; the same predicate is what makes /sys/power/disk read [disabled]. Raising a test machine's lockdown to integrity reproduced both readings and the false success. An image size that exists but does not read was a second way to say yes: named bare in the arithmetic comparison it counts as zero, and any swap at all beats zero. The sysfs, swaps and resume-config paths take an override the way omarchy-power-present does, so the test can construct a kernel that refuses. 🤖 Generated by Opus 5 in Claude Code. Reviewed by Codex XHigh. Co-authored-by: Codex XHigh <codex@openai.com>
Stopping a recorder this script did not start, with no saved pid and no recording file, still finalized and posted "Screen recording saved" for an empty name: a broken "-preview.png" thumbnail and a click that opens nothing. Now that the whole script runs under one lock, that is the last way the empty-name toast from omacom#11508 is reached. Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
…om#15093) * Stop reloading a local plugin on its own Python bytecode writes The local plugin watcher reloads a plugin on every write under its directory. A plugin whose Python helper imports modules from that directory makes CPython write __pycache__/*.pyc, each write reloads the plugin, the reload restarts the helper, and the helper's next lazy import writes the next .pyc. The 150ms debounce coalesces a burst but cannot break that cycle, since each write comes from the helper the previous reload started. Ignore paths under __pycache__ (which covers the temp name CPython writes before renaming) and stray .pyc/.pyo files. Hidden files inside a plugin are still watched: entry points may live there, and the manual promises a reload for any saved file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Ignore only __pycache__ below a plugin, not names that look like bytecode Matching .pyc/.pyo and __pycache__ against the whole plugin-relative path also matched plugin directories themselves: moving in a plugin whose id is acme.pyc (a valid id) was ignored, as was every change to a plugin dir named __pycache__. Python 3 writes bytecode only into __pycache__, so the suffix check was never needed for the reload loop; drop it and require __pycache__ to sit inside a plugin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…omacom#17000) * Let one sudo password last ten minutes in a terminal Omarchy commands revoked sudo's timestamp on entry and exit and authenticated through a sudo -N wrapper, so every privileged step asked again: three prompts at "Create system snapshot", six for a dev link session. Ship timestamp_timeout=10, drop the revocation and the wrapper, and keep omarchy update's single authorization and keepalive. Channel switching keeps its stop for a destination older than this tree, now keyed on what the next steps need: omarchy-update-pacman, and an updater that restores the caller's PATH. Releases 4.0.5 and 4.0.6 have neither. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Make update, refresh and channel switching plain scripts again The privileged-Bash startup check, environment scrubbing, OMARCHY_PATH source-root check and pinned PATH in omarchy-update, omarchy-refresh-pacman and omarchy-channel-set only guarded against code already running as the user, the same threat the password boundary was dropped for. They return to plain Bash as in 4.0.6, with every feature since kept; hooks and mise inherit the caller's PATH directly. The channel swap calls pacman itself again, so a refresh that installs an older release without omarchy-update-pacman cannot strand it, and the older-destination stop is no longer needed. Leaving dev drops the unlinked checkout's bin from PATH so the packaged update runs the packaged helpers. omarchy-update-stay-awake and omarchy-sudo-passwordless keep the security library: OM-SEC-12 and OM-SEC-01 guard against other accounts, not the caller. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: David Heinemeier Hansson <david@hey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com> Co-authored-by: Mark Groves <mark-groves@users.noreply.github.com>
* Report each display's refresh rate in the monitor panel state Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Offer a display's refresh rates below its resolution in the monitor panel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
omacom#17177) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…om#17179) * Slide background changes on every monitor without a black flash Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Cover the multi-monitor background reveal and its hand-off Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…tream (omacom#14585) With nothing playing, the media service fell back to the first player holding a PipeWire stream, even one the bar refuses to show. An idle Chrome that once played media keeps a Stopped MPRIS session with only art and length, so pausing another player handed it the selection and the widget vanished with nothing left to click. The idle fallback now prefers a player with a title or artist over one without, unless the hidden one is the player the user last chose, so cycling sources onto it still works. It moves into MediaModel.js so the tests exercise the selection itself. Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Codex Medium <noreply@openai.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…14514) * Let the Bitwarden extension popout keep the size it asks for The extension window was tagged floating-window, which forces every window carrying it to 875x600. Bitwarden opens its popout at the width chosen in its settings (380, 480 or 600) and a height of 630, so the forced size left it the wrong shape. Float and centre it directly instead, keeping no_screen_share. Co-Authored-By: Codex Medium <noreply@openai.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Match the Bitwarden extension popout in every Chromium browser The rule matched only chrome-<id>-Default, so the popout in Brave (brave-<id>...), in a second Chromium profile (-Profile_1) or with the popup path appended (__popup_index.html) got none of it: no float and no screen-share protection, and Brave tiles it into a wide, half-drawn window. Matching on the extension ID alone covers them, as omacom#8341 does. The test is adapted from omacom#8341's, keeping its float and screen-share checks and asserting that no size or size cap is set. Co-Authored-By: Ty Richards <me@tyrichards.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Drop the Bitwarden rule test The test restated the two declarative rules in bitwarden.lua and counted them, so it guarded nothing a reader of the file cannot see and broke whenever a rule was added, which AGENTS.md asks tests not to do. The broader `.*nngceckbapebfimnlniiiahkandclblb.*` match stays: the popout's class is `brave-...` in Brave and ends in `-Profile_1` in a second Chromium profile, and on quattro those popouts tile because the old exact class never matches them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Codex Medium <noreply@openai.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Ty Richards <me@tyrichards.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Add Hex as a selectable dictation backend Hex (https://anoma.ly/hex/) installs from the AUR's hex-bin, downloads its speech model during setup, and runs as the hex.service user unit. Omarchy's push-to-talk and toggle keys drive it through `hex dictation start|stop|toggle`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Type Hex transcripts through Omarchy so they land in terminals too Hex pastes with a bare Ctrl+V through wtype, which terminals ignore. Stop with `hex dictation stop --print` instead and type the transcript with omarchy-clipboard-paste-text, the way the other backends insert text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Install Hex from Omarchy's package repository hex-bin is packaged in omarchy-pkgs, so install it with omarchy-pkg-add instead of from the AUR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test Hex setup and removal Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Give the Hex ready notification its glyph Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…#15126) Hyprland 0.56's keybind:unbind() removes every bind on the handle's chord, not just the handle's own, so closing the region picker took any user bind on RETURN, CTRL + RETURN, TAB, CTRL + TAB or the arrows with it until the next reload. The picker's binds are now created once per config load and switched on and off with set_enabled(), which leaves other binds on the same chord alone. They carry no description, so the keybindings menu does not list them while they are off. Any unbind of one of those chords expires the cached handle, and in 0.56 every handle method but tostring() dereferences an expired handle and aborts the compositor. So each handle is checked through tostring() before use and re-created when it has expired. Fixes omacom#12546 Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Codex Medium <noreply@openai.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…14183) Claude-Session: https://claude.ai/code/session_01DMKCCA2jSkTTwEwdZepjQd Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Preserve terminal font size when changing font family omarchy-font-set rewrote the Foot font line with a hardcoded size=9, silently undoing the size chosen by omarchy display text size. Now the existing :size=N is kept (falling back to 9 when absent), matching the behavior of kitty, alacritty, and ghostty. Fixes omacom#6957 * Resolve the test font deterministically via fc-match * Harden font size test for minimal environments * Keep the primary Foot font's size when the line lists fallbacks Foot's font= takes a comma-separated fallback list, and the greedy match took the last :size= on the line, so a fallback's size replaced the one omarchy-display-text-size had set on the primary font. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Stub fc-list in the font-set size test The test picked a family with fc-match under the real HOME and then had omarchy-font-set validate it with fc-list under the temporary one, so a font installed only in the user's home, or fontconfig with no fonts, failed the test for reasons unrelated to size. A fixed family answered by a stub makes it hermetic and removes the skip that reported as a pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: David Heinemeier Hansson <david@hey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
omacom#14103) * Leave a dangling shared symlink alone when setting up an agent account Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Only skip a dangling shared link, and test failed-setup cleanup Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test failed account setup error --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com>
* Paint symbolic tray icons in the bar foreground through their alpha MultiEffect's colorization multiplies the source's luminance by colorizationColor, so a symbolic icon with a dark fill (Adwaita's #2e3436, Cryptomator's #222222) stayed dark on a dark bar. Fill a rectangle with the foreground and mask it by the icon instead, so the icon's own colour is discarded. The mask ramps smoothly over the icon's alpha (threshold 0.5, spread 1.0) rather than the default hard cutoff, which turned every anti-aliased edge pixel opaque. The mock tray item takes its icon from the environment so the new test can publish a dark symbolic icon through a real StatusNotifierItem. The test grabs the icon itself, checks every opaque pixel is the foreground and a corner stays transparent, and skips when the output is asleep, since a grab then never returns. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Check that a symbolic tray icon keeps soft edges The mask ramps over the icon's alpha so anti-aliased edges stay partly transparent, but the test only looked at opaque pixels and one corner, so a hard cutoff that fattens the icon still passed. Require at least one partly transparent pixel in the grab. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
) cyclenext walks Hyprland's z-order vector and bringactivetotop rotates the active window to the back of that same vector, so raising on the way back put the window just left exactly where "previous" looks next and focus ping-ponged between two windows. Lowering the window being left instead of raising the one being landed on keeps the newly focused window on top and still steps one window per press, so the chord stays the inverse of Alt + Tab.
…igration (omacom#13432) * Undo Compose's $$ escaping when migrating a legacy Windows VM password The legacy compose under ~/.config/windows holds the password as Compose reads it, so a $$ there reached the guest as $. Migration copied the raw text into the RDP credentials and re-escaped it for the new compose, leaving RDP and the new container environment with $$ while the existing guest, whose disk is preserved, still has $. Decoding $$ at the migration boundary keeps both on the password the guest actually has. This also makes omacom#4882 safe to land on dev, which writes every $ in the password as $$. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Undo the legacy password's YAML escapes too when migrating Compose parses the legacy PASSWORD as a YAML double-quoted string before it interpolates $$, so a legacy "a\\b\"c$$d" reached the guest as a\b"c$d. Decoding only $$ left \\ and \" in the RDP credential and the rewritten compose. unescape() already reverses exactly these layers for every other read of the compose, so use it here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: omarchybot <omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com>
omacom#14684) * Use the latin1 console keymaps for German and French in the setup form The kbd `de`, `fr` and `fr_CH` keymaps are the old 7-bit national variants: `de` puts @ [ ] where ü ö ä belong, `fr` puts { } | where é è ù belong, and `fr_CH` leaves the accented keys unassigned. The installer loads the chosen keymap on the console, so a German or French user could not type their own letters in the name or password fields. The `-latin1` maps are the standard layouts, and systemd derives the same XKB layout from them, so the installed desktop is unchanged. Fixes omacom#8680 Co-Authored-By: Codex Medium <noreply@openai.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test that both French entries take their latin1 console maps Only German was asserted, so reverting French or French (Switzerland) to `fr` or `fr_CH` passed the suite. Folds in the French assertion from omacom#15003, extended to French (Switzerland), which only this pull request changes. Co-Authored-By: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Codex Medium <noreply@openai.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…acom#16385) * Count Codex sessions it has compressed to .jsonl.zst Codex 0.163 compresses a rollout it considers finished to .jsonl.zst and deletes the plain file, so the scan's *.jsonl glob found nothing and every local stat in the Codex tab stayed at zero. Read both, through Python 3.14's compression.zstd. Codex publishes one form before removing the other, in both directions, so for a moment a session exists twice; the plain file is the one Codex reads, and the only one counted. Co-Authored-By: Dennis Gram <48596094+dennisgram@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fail the compressed-session tests when their fixture is not in place The script runs without set -e, so a zstd call that failed left the fixture in the wrong form and the assertion after it passed against quattro's collector, or without the both-forms filter. Each fixture now checks it has the files it means to test. Co-Authored-By: Codex Medium <noreply@openai.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Read compressed Codex rollouts through collectors.py's guarded zstd import collectors.py already imports compression.zstd under a guard, leaving zstd None on a Python without it, as DeepSeek's reader expects. A second, unconditional import made that guard dead and would stop every collector loading on such an interpreter. Without zstd, a .jsonl.zst rollout is now one that couldn't be read, like a damaged one, rather than an error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: muse-wonder High <noreply@meta.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Dennis Gram <48596094+dennisgram@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com> Co-authored-by: muse-wonder High <noreply@meta.com>
* Let the Lua assertions in shell tests fail Handing a heredoc to lua with no script argument runs it as a REPL. An error prints a traceback and the interpreter still exits 0, so eight assertions across two files could not fail their tests: five checking that the Hyprland bootstrap clears cached modules, three checking that saved workspace layouts load. They have been passing on their own merits, which is luck rather than coverage. Read the heredocs as scripts with an explicit -, and check the exit status where the Lua assertions are the only assertions. base-test.sh does not set -e, so a nonzero exit alone would still have left the pass below to run. The four remaining call sites hand their output back for the shell to grep, so their failures already bit. Switched anyway, so the next assertion written in one is not born dead. Added a style test for it, since nothing about the working form advertises why it matters. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Read the Lua heredocs quattro gained since as scripts too hw-nvidia-test, screensaver-workspace-test and shell-shortcuts-test each landed on quattro with a bare `lua <<'LUA'`, which the new style test refuses. All three hand their output back to the shell, so their failures already bit; switching them keeps the guard green and the next assertion written inside one armed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fail the binding checks that only assert absence when Lua errors These three read the bindings Lua prints and pass when a binding is missing, so a Lua error that prints nothing passed them too. Now that the heredoc runs with lua -, its exit status says whether the config loaded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Say why a bare Lua heredoc cannot fail, and catch it without a space lua with no script argument is not a REPL when stdin is not a terminal: it runs stdin with dofile and discards the error status, so it exits 0. The guard also missed lua<<'LUA', which Bash accepts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Run quattro's new Lua assertion blocks as scripts hyprland-startup-cursor-test.sh and dictation-test.sh arrived on quattro with three bare lua heredocs made only of assertions, so none of them could fail, and shell-test-style-test.sh fails on them. Each now runs as lua - and fails its test on Lua's exit status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Arm the Lua heredocs quattro added in the hold-binding and JIS tests bind-hold-test.sh is made only of Lua assertions, so as a bare heredoc none of them could fail; it now runs as lua - and fails on Lua's exit status. hyprland-jis-bindings-test.sh hands its output back for comparison, so it switches to lua - to keep the next assertion written there from being born dead, and to satisfy shell-test-style-test.sh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Name the JIS case whose Lua failed Now that fire() exits nonzero on a Lua error, set -e would end the test at the command substitution with no not-ok line; failing there names the binding that broke. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fail the uninstalled-backend and keyboard layout checks when their Lua errors The uninstalled dictation backend check only asserts that no dictation binding is printed, so a Lua error printing nothing passed it, as the absence checks armed earlier did. The keyboard layout resolver's captures discarded its status too, so an error after the expected output still compared equal; both now fail the way the JIS captures do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Move the Lua heredoc guard into the test runner's test Omarchy's AGENTS.md asks for a new check to extend the area's existing test file rather than add a *-test.sh, and test-runner-test.sh is where the suite's own health is tested. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Omabot <david@hey.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Codex Medium <noreply@openai.com>
* Restore gvfs after resume from a transient unit instead of a background subshell The post hook backgrounded its gvfs-daemon restart, but systemd kills everything left in systemd-suspend.service's cgroup when the unit finishes, so the restart never ran and /run/user/$UID/gvfs stayed unmounted after every resume. Where user sessions are frozen, the leftover child instead held up the thaw for about 90 seconds. Hand the restart to a systemd-run timer unit that lives outside that cgroup, and run it as the user with --uid rather than sudo, which goes through PAM and stalls on a fingerprint prompt nobody can answer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fire the gvfs restart within a second of its delay A transient timer inherits AccuracySec=1min, so the restart could land anywhere up to a minute after resume, leaving the FUSE gateway down that long. The test now also checks the scheduling arguments and fails if the hook itself fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> * Say when the gvfs scheduling check had no user bus to check Without a user bus under /run/user the loop asserts nothing, so report it as skipped rather than passed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
* Document quiet Limine menu for dual boot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Say how to reach Limine when Direct Boot is on With Setup > Direct Boot the firmware launches the Omarchy UKI without stopping at Limine, so pressing a key never shows the menu. Point to the firmware boot menu or turning Direct Boot off, as the snapshots guide does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
* Say what the security manual's defaults actually are The Security chapter called full-disk encryption mandatory, while Getting started documents opting out at the formatting confirmation, and said all incoming traffic is blocked except LocalSend, while the firewall also admits DNS from Docker networks and UFW's built-in multicast DNS rule answers for Avahi. State the opt-out and the three exceptions. Translations are left to the catalog sync. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Don't call the firewall's exceptions a complete list UFW's stock before.rules also accept ping, DHCP replies and UPnP discovery ahead of Omarchy's own rules, so "three exceptions" told a reader everything else was blocked. The Docker DNS rule also admits all of 172.16.0.0/12 and 192.168.0.0/16 rather than only the host's containers, so it is described by the address it answers on and the ranges it accepts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Codex Medium <noreply@openai.com>
* Fix additional assorted typos in navigation * Call it the file manager, as the rest of the manual does The app is Files, but the hotkeys table and the GUIs page both call what Super + Shift + F opens the file manager. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Put the blank line back before the four-way tiling image Resolving the conflict with quattro moved the blank line above the "Now try" paragraph and left the image with none before it, so Markdown folds it into that paragraph instead of giving it a block of its own like every other image on the page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Upstream
quattromoved fromcf71857c(omacom#17103, 30 Oct) tod367a568(omacom#17201, 31 Oct). 69 first-parent commits, all replayed onto forkquattro, including merges omacom#17156, omacom#17158, and omacom#17160 via-m 1. One conflict, on omacom#17000. Nothing skipped. Fork delta vs this tip is 214 paths (was 215). Face, Grok Bot, and Cursor stay.FaceChromeCanvasstays immediately beforeFilterInput. Power profile stays onbusctl, and the menu provider stays out. Cursor stays the official tarball.linuxandlinux-headersstay ininstall/omarchy-other.packages.Sudo
Omarchy commands no longer revoke sudo on the way in and out, and the no-update wrapper is gone. One password lasts ten minutes in the same terminal (
etc/sudoers.d/omarchy-sudo-timeout).omarchy updateasks once after confirmation, insidescript's own terminal, and a keepalive refreshes that timestamp through the boot check. Update, refresh, and channel switching are plain scripts again; hooks and mise see the caller's PATH. Channel switching installs theomarchy/omarchy-devpair withpacman -Sitself, so a refresh that landed an older release cannot strand the switch (omacom#17000).Grok Bot and Cursor product updates stay in the pipeline, after AUR and before the boot check, and they share that one authorization. The boot check is still the last sudo-capable step.
Displays
The display panel shows one screen at a time, with a layout map (omacom#17159). Monitors resize without overlap, and older
monitors.luafiles are migrated (omacom#17166).monitors.luacan turn the panel's saved settings off (omacom#17169). A right-click on the layout map rotates a monitor (omacom#17170). The panel offers refresh rates (omacom#17175). The template only carries what the panel does not already write (omacom#17177). An HDR display stays in SDR while a window is fullscreen (omacom#17157). A popped-out window is centered again when it moves to another monitor (omacom#14549).Shell, boot, and Hyprland
Restarting the shell waits until every stopped instance, including worktree shells, has exited (omacom#17160). First boot draws the ISO's traced-icon progress screen (omacom#17156). Apple Silicon loads Omarchy's shell setup (omacom#17041), and the bashrc migration keeps an earlier
~/.bashrc.bak(omacom#17158). Hyprland animations are a fifth quicker, back to the earlier feel (omacom#17144). The system bell is muted so terminals stop chiming on BEL (omacom#17152), and Hyprland's support popup is off (omacom#17153). The pointer is parked off a dropdown list before a keyboard walk (omacom#17117). Background changes slide on every monitor without a black flash (omacom#17179).Dictation, agents, and hardware
Dictation toggles on Alt + Space and push-to-talk is Right Alt (omacom#17188). Hex is a selectable backend (omacom#17186). The Agents panel counts Codex sessions compressed to
.jsonl.zst(omacom#16385). Setting up an agent account leaves a dangling shared symlink alone (omacom#14103).--reauthwithout an account is refused instead of adding one (omacom#14100), and the rename hint names the provider (omacom#14099). Wildcat Lake gets Intel hardware video decoding (omacom#17150). The realtime repair is skipped when the installedomarchypackage predates it (omacom#17096). Vendor hotkey keyboard devices are ignored (omacom#9129). Hibernate is hidden when the kernel will not accept it (omacom#7779). Resume restores the gvfs FUSE gateway (omacom#14496).Smaller fixes
Bar tooltips stay hidden until their surface has the output's scale (omacom#16243). Dark symbolic tray icons paint in the bar foreground (omacom#14661). A battery draining on AC at 100% is not called fully charged (omacom#16278). A notification click focuses a multi-word sender's window (omacom#16380). The image picker notices a file overwritten in place (omacom#15079). Night light resets to the identity matrix when it turns off (omacom#14489). CPU usage is read from
topin the C locale (omacom#15109). A DDC display whose brightness cannot be read is still remembered (omacom#14525). The media widget stays on a paused track when an idle player holds a stream (omacom#14585). A Bitwarden extension popout keeps the size it asks for (omacom#14514). The screenshot picker does not unbind the user's own keys (omacom#15126). A local plugin does not reload on its own Python bytecode writes (omacom#15093). Stopping a recording that was never saved says so (omacom#15073). A new terminal opens in HOME when the focused window is not a terminal (omacom#15007). Changing font family keeps the terminal's font size (omacom#6958). Alt + Shift + Tab cycles backwards through every window (omacom#8576). A legacy Windows VM password with$$survives the Quattro migration (omacom#13432). German and French setup use the latin1 console keymaps (omacom#14684). Inkscape's file choosers float (omacom#15792). Dropbox installslibappindicatorunder its current name (omacom#15076), the status poll no longer voids a pending login link (omacom#15135), and 360–364 days is no longer "0y ago" (omacom#14183). Docs cover broken session environment files (omacom#10708), the quiet Limine menu (omacom#16369), Rufus for Windows ISO writes (omacom#16383), and what the security defaults actually are (omacom#16155). Catalogs run through omacom#17201.Tests
Passed:
update-sequence,update-hook-security,update-boot-verify,update-lockwas not this tree (same failure on quattro: no/run/user),update-disk-space,update-user-path,channel-switch,channel,sudoers,security-source-root,region-refresh-boundary,menu,i18n,hibernation-available,system-stats,hyprland-monitor-settings,hyprland-pop,capture-picker-binds,unmount-fuse-hook,./test/cli.update-stay-awake-securitystopped on a missing private XDG runtime directory.tray-symbolic-iconskipped (no Wayland compositor). Topic draft #94 was left alone. No other open sync.