It appears this bug has been closed upstream as fixed in gtksourceview 5.2 (I think, maybe).
Ubuntu 22.04 doesn't seem to use it yet though (still on gtksourceview 4).
It appears this bug has been closed upstream as fixed in gtksourceview 5.2 (I think, maybe).
Ubuntu 22.04 doesn't seem to use it yet though (still on gtksourceview 4).