Colomban Wendling

> It accepts {} initialization on `another` though. Does it? doesn't seem to show for me.

There's https://github.com/codebrainz/geany-zencoding, but that's very old… not sure if there's something more current.

Yep, and even an old report at that: current Debian doesn't have *gdb-python2* anymore. I guess the reason why the debugger plugin is not in current Debian stable is rather...

> Anyway, seems like only solution is self-compile? Or is somebody in contact with package maintainers? Yes the only solution is to self-compile for the moment. Debian won't likely propose...

Hum indeed I don't see it in the repo, yet I though I did earlier… oops. Anyway, they have a version that would have worked, so I don't know why...

@elextr yeah, I should have made them on the PR integrating the parser to UCTags, but I missed that train. I'm commenting here because it's an opportunity, but yes any...

Currently it's hard-coded to a 500×200 default size, and if resized the new size doesn't survives a Geany restart. There's 3 things I could do: 1. adapt that default size...

What your change suggests to me is that you'd encounter cases where `document_get_current()` doesn't return the document for which the signal was fired for. This sounds weird for the `activate`/`new`/`open`/`reload`/`filetype-set`...

I can't reproduce either (tested GTK2 just now). What is your *exact* GTK versions, system, desktop, etc.?

I can't reproduce in 1.37/current master. What you have is [zero-width-space (U+200B)](https://en.wikipedia.org/wiki/Zero-width_space) followed by a newline (U+0A). Nothing too weird here, and nothing that I would expect Geany to crash...