[GH-ISSUE #629] Markup escape issues #3019

New issue

Closed

opened 2026-05-22 23:53:16 +01:00 by JakeStanger · 0 comments

JakeStanger commented

2026-05-22 23:53:16 +01:00

Owner

Originally created by @JakeStanger on GitHub (Jun 3, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/629

Describe the bug
#586 introduced Pango support to more places. In some places, the text needs to be (intelligently) escaped, as it is now causing blank strings and GTK warnings.

To Reproduce
Steps to reproduce the behavior:

Add the music module with default settings
Play a song with an & in its title (or where the artist has an &)
Observe GTK warning

Expected behavior

The & is correctly escaped. Markup continues to work as expected.

Additional context

Glib offers a markup_escape_text which will correctly escape Pango markup. This cannot be used on the full string as this then...escapes the markup.

Originally created by @JakeStanger on GitHub (Jun 3, 2024). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/629 **Describe the bug** #586 introduced Pango support to more places. In some places, the text needs to be (intelligently) escaped, as it is now causing blank strings and GTK warnings. **To Reproduce** Steps to reproduce the behavior: 1. Add the music module with default settings 2. Play a song with an `&` in its title (or where the artist has an `&`) 3. Observe GTK warning **Expected behavior** The `&` is correctly escaped. Markup continues to work as expected. **Additional context** Glib offers a `markup_escape_text` which will correctly escape Pango markup. This cannot be used on the full string as this then...escapes the markup.

JakeStanger closed this issue

2026-05-22 23:53:16 +01:00