Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-09-13 | XlibDraw: verticalOffsets in XConf not needed | jao | |
2022-09-12 | X11.MinXft not needed anymore | jao | |
2022-09-12 | wee refactoring: a couple type synonyms | jao | |
2022-09-11 | x event loop clean-ups | jao | |
2020-11-15 | Fix crash on <fn=1>x</fn> when no additional fonts are specified | Tomas Janousek | |
This fixes the following crash that happens with the default xmobar configuration (using HOME=/ makes xmobar ignore ~/.xmobarrc): $ echo "<fn=1>x</fn>" | HOME=/ xmobar xmobar: Prelude.!!: index too large Commit 3e9e1cb9d300 ("Fix crashes/busy looping happening via index") meant to fix this but apparently it only fixed indexing of fontlist, not voffs, so the crash was still there. Fixes: https://github.com/jaor/xmobar/issues/504 | |||
2020-05-10 | Fix crashes/busy looping happening via index | Sibi Prabakaran | |
Right now, with the `StdinReader` plugin enabled - you can crash/cause busy looping of xmobar if the following html file is opened: ``` <html> <head> <title>hello <fn=1>string</fn> </title> </head> </html> ``` More details about this bug is here: https://github.com/jaor/xmobar/issues/442#issuecomment-625706001 This MR also fixes another bug which produces a crash in xmobar if you pass non integer items between fn: <fn=crash> | |||
2018-11-25 | X11.XUtil -> X11.Text | jao | |
2018-11-25 | Xmobar.App.Defaults and Xmobar.Config.Types | jao | |
2018-11-25 | Back to app/src, since it seems they're the default convention for stack | jao | |