Fourth release of today: #fnott 1.8.0 ๐ฅณ
### Added * `progress-style` configuration option with possible values of `bar` (previous behavior) and `background` which shows the progress as the background color. * Fish shell completions. ### Changed * Default icon theme from `hicolor` to `default`. ### Fixed * Crash when...
Happy release day! ๐
* #yambar: https://codeberg.org/dnkl/yambar/releases/tag/1.10.0
* #fuzzel: https://codeberg.org/dnkl/fuzzel/releases/tag/1.9.2
* #fnott: https://codeberg.org/dnkl/fnott/releases/tag/1.4.1
Last day of my vacation. Fingers crossed I can do a #foot release later today as well!
#fnott 1.4.0 has been released! ๐
Format strings for #fnott!
Don't want the application name in the notification? Set "title-format=".
Want to customize the markup? The new *-format options recognize "<b>", "<i>" and "<u>".
This patch adds three new per-urgency options: * `title-format` (default: `%a%A`) * `summary-format` (default: `%s\n`) * `body-format` (default: `%b`) These options allows us to configure the rendered strings in the notification. The following formatters, and escapes are recognized: * `%a` - the application name/title * `%s` - the notificationโs summary * `%b` - the notificationโs body text * `%A` - actions indicator, `*` if notification has actions, the empty string otherwise * `%%` - a literal `%` * `\n` - a newline Markup is also supported: `<i>`,`<b>` and `<u>`. Note that each section (title/summary/body) is always rendered at the beginning of a new line. I.e. the format strings are *not* expected to end with a `\n`. That is, given this configuration (the default): ```ini title-format=<i>%a</i> summary-format=<b>%s</b>\n body-format=%b ``` the notification will be rendered like this: ``` โญโโโโโโโโโโโโโโโโโโโโฎ โ Application title โ โ Summary โ โ โ โ Body text โ โฐโโโโโโโโโโโโโโโโโโโโฏ ``` However, if a format string is set to the empty string, it is completely removed. For example, if we have ```ini title-format= ``` Then the notification will be rendered as: ``` โญโโโโโโโโโโโโโโโโโโโโฎ โ Summary โ โ โ โ Body text โ โฐโโโโโโโโโโโโโโโโโโโโฏ ``` (and *not*) ``` โญโโโโโโโโโโโโโโโโโโโโฎ โ โ โ Summary โ โ โ โ Body text โ โฐโโโโโโโโโโโโโโโโโโโโฏ ``` Closes #39
My project #fnott (notification daemon) uses #nanosvg to render SVG icons.
I've always thought the rendered icons looked bad, compared to the ones rendered by librsvg. I chalked it up to nanosvg being "simple stupid" [sic].
Turns out /I'm/ stupid.
Nanosvg produces RGBA output that is NOT pre-multiplied.
But, pixman expects pre-multiplied color channels.
Blend a non-premultplied image as if it was pre-multiplied, and the result is, well, crap.
dnkl
dnkl 
fedops ๐๐