xmobar/src/Xmobar, branch master

changelog and copyright updates

2026-06-27T16:48:17Z

remove " &" and fix zombie processes

2026-06-26T19:59:27Z

" &" was to avoid throwing an exception when the child process has a non-empty exitcode. However, the error-throwing function is callCommand and not spawnCommand, so removing " &" shouldn't change the semantic. https://codeberg.org/xmobar/xmobar/pulls/698#issuecomment-1722323 > callCommand seems to be the closest new function to system, but there > is a difference: it raises an exception if the child process has a > non-zero exit code. To preserve the exact behavior would require > something like spawnCommand (s + "&") >>= waitForProcess. I was able to reproduce zombie processes with the following steps: + running my own xmobar configuration + spawning a command that is long running (sleep 10) + sending SIGTERM to the xmobar process After doing so, the sleep command will continue to run. This PR uses withCreateProcess, which will always wait for the process to terminate, even when the main thread is asked to exit (SIGTERM). Note that SIGKILL is not expected to terminate the children.

use Int instead

2026-06-23T19:41:59Z

pass remaining battery percentage to low battery command

2026-06-23T19:41:59Z

guard low battery alert behind heuristics

2026-06-22T14:42:02Z

Previously low battery alerts only depend on the ac variable. The ac state that is rendered (racst) follows more heuristics. However this causes a discrepancy where xmobar can show the status is charging while continue to spawn low battery alerts. This PR fixes that by using the rendered ac state to decide whether the alert is sent.

Fix PacmanUpdates parse error on GHC < 9.8 - fix #766

2026-06-16T19:47:23Z

Export-list DEPRECATED pragmas were only added in GHC 9.8 (proposal `#134`[1]). On older compilers the pragma inside the export list is a parse error ("parse error on input '{-# DEPRECATED'"), breaking the build. Guard the pragma with CPP so it is only emitted on GHC >= 9.8. The export-list form is kept deliberately: it deprecates only the `pattern PacmanUpdates` export, leaving the equally-named `PacmanUpdates` type untouched, so downstream users referencing the type get no spurious deprecation warnings. On older GHC the compile-time warning is simply absent; the runtime "deprecated plugin" note still informs users. [1]: https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0134-deprecating-exports-proposal.rst

Allow predicate based kernel checks in PacmanUpdates

2026-06-16T17:51:56Z

PacmanUpdates previously supported either no kernel update detection or matching a single kernel package name. That works for Arch's `linux` package, but not for Manjaro's series specific kernel packages such as `linux618` or `linux70`. Replace the Bool indexed API with an explicit kernel check kind and add `PacmanUpdatesPredicateK`, which accepts a `String -> Bool` predicate for detecting kernel updates from the package list.

Fix Brightness plugin - fix #775

2026-05-29T20:30:43Z

Skip root pixmap access when alpha == 255

2026-05-29T08:31:36Z

When alpha is 255 (fully opaque), the pseudo-transparency blend factor is zero (0xFFFF - 257 * 255 = 0), making the root pixmap composite a visual no-op. However, drawBackground unconditionally calls XRenderCreatePicture on the _XROOTPMAP_ID pixmap. Wallpaper setters like feh free the old root pixmap via XKillClient each time they cycle to a new image. If xmobar attempts XRenderCreatePicture on the freed pixmap, the X server returns BadDrawable and the default error handler terminates xmobar. Guard the entire root pixmap code path with `when (alpha < 255)` so that fully opaque bars never touch _XROOTPMAP_ID.

hlint warnings

2026-05-07T00:05:54Z