Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-04-18 | Split up battery reading functions; fixed units | Patrick Günther | |
Every quantity is now read in its own function and Maybe and pattern matching is used for dealing with absent files. On top of that all units should be fixed now. | |||
2022-04-16 | Fixed unit of battery power consumption | Patrick Günther | |
2022-04-14 | Memory: new argument to scale usage units | jao | |
Fixes #624 | |||
2022-04-13 | make small refactoring of load linux code | Michal Zielonka | |
Add <$> for parsing content of file. | |||
2022-04-12 | Changelog | jao | |
2022-04-11 | add load monitor for freebsd | Michal Zielonka | |
2022-03-30 | Fix: consistent use of configured nastring instead of hardcoded N/A | jao | |
2022-03-30 | Changelog and version bump | jao | |
2022-03-30 | Wee clean-ups | jao | |
2022-03-30 | Load: honour the -d (decimal digits) monitor argument | jao | |
2022-03-30 | Load monitor: correctly colorize according to -L/-H | jao | |
2022-03-30 | Load: new load average monitor | jao | |
Closes #208 | |||
2022-03-29 | Apply hlint suggestions to MultiCoreTemp | Rob Whitaker | |
2022-03-29 | Fix MultiCoreTemp's temperature file finding logic | Rob Whitaker | |
Instead of searching for a fixed set of files and directories (numbered 0-9), which would miss anything above 9, it now searches the relevant directories for files matching the right pattern, regardless of number. Fixes #616. | |||
2022-03-27 | base < 4.17 to allow ghc 9.2.2 | jao | |
Fixes #617 | |||
2022-03-24 | Link to jao/xmobar-config | jao | |
2022-03-24 | typo | jao | |
2022-03-24 | readme nits | jao | |
2022-03-01 | examples and changlog updated0.42 | jao | |
2022-02-20 | Documentation: Note the need for threaded RTS with QueueReader & xmonad | Tomas Janousek | |
Related: https://github.com/jaor/xmobar/issues/571 | |||
2022-02-20 | Documentation: More robust QueueReader example | Tomas Janousek | |
1. Call `initThreads` early because there's no guarantee the xmobar thread will do this before xmonad makes any Xlib calls (although it's likely as xmonad startup is probably more expensive). 2. Use `forkOS` to fail early if running in a non-threaded RTS. Also, xmobar's own main thread would normally be a bound thread, so this may (likely non-observably) result in more consistent behaviour. Related: https://github.com/jaor/xmobar/issues/571 | |||
2022-02-20 | Documentation: Drop unused fragment in QueueReader example | Tomas Janousek | |
Related: https://github.com/jaor/xmobar/issues/571 | |||
2022-02-19 | More documentation nits | jao | |
2022-02-19 | Documentation nits | jao | |
2022-02-19 | Documentation: shuffling around the DBus xmonad example | jao | |
2022-02-19 | Documentation: dbus section moved | jao | |
2022-02-19 | Interfacing with window managers: new doc file | jao | |
2022-02-19 | Documentation whitespace and titles | jao | |
2022-02-19 | Strip new lines from X log messages (issue #590) | jao | |
2022-02-18 | Apply hlint suggestion | Tomas Janousek | |
Fixes: b7ca54651bb1 (""bright" ansi colour names") | |||
2022-02-18 | Changelog updates | jao | |
2022-02-17 | Refactoring: Clean up naming of X11 event loop threads | Tomas Janousek | |
What used to be called `eventLoop` didn't process any X11 events at all, rename to `signalLoop` to signal that it really deals just with xmobar signals. | |||
2022-02-17 | Fix memory leak in drawInWin | Tomas Janousek | |
In f8c835a33a7a, I flipped the discard flag to XSync to False on a false assumption that it may discard events from under the eventer thread (since renamed to handleXEvent). This can't happen—the eventer thread and the main loop do not share a Display connection, they have two separate ones. Turns out, the main loop doesn't read/process any events from its Display connection, which is why it was necessary to discard them once in a while. The fix restores that discarding, adds a comment to explain why that discarding should stay, and just to make things a bit cleaner, also prevents some of those events from being emitted in the first place: by configuring the graphics context that we don't want any exposure events (https://tronche.com/gui/x/xlib/events/exposure/graphics-expose-and-no-expose.html). Fixes: f8c835a33a7a ("Fix delayed reaction to USR1/2 signals") | |||
2022-02-13 | Use nh' for displaying the bar on the bottom of the screen. Fixes #555 | exorcist365 | |
2022-02-09 | "bright" ansi colour names | jao | |
See #606 for further discussion | |||
2022-02-08 | Lower aeson version limit | jao | |
2022-02-08 | Missing help bit: -TSwaybar | jao | |
2022-02-08 | Linting | jao | |
2022-02-08 | Documentation bits and version bump | jao | |
2022-02-08 | pango output: fonts | jao | |
2022-02-07 | swaybar-protocol: additionalFonts via pango markup | jao | |
2022-02-07 | swaybar-protocol: boxes working | jao | |
2022-02-06 | Whitespace in the Draw.hs mess | jao | |
2022-02-06 | swaybar-protocol: borders (but not quite working as expected) | jao | |
2022-02-06 | swaybar-protocol: support for clickable Action | jao | |
2022-02-06 | Little refactoring: forkThread | jao | |
2022-02-06 | swaybar-protocol: output with colors and actions | jao | |
2022-02-06 | swaybar-protocol: very basic format | jao | |
2022-02-06 | quick-start.org: indentation and reordering | jao | |
2022-02-04 | Refactoring: event loop handling simplifications | jao | |