Might be version of GTK3 dependent, works fine for me
`10:34:45: Geany INFO : GTK 3.18.9, GLib 2.48.2`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1893#issuecomment-403176
LGBI, but I don't use Python so much lately.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1894#issuecomment-403171563
Fixes https://github.com/geany/geany/issues/1351
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1894
-- Commit Summary --
* Update Python identifiers with Python 3.7
-- File Changes --
M data/filedefs/filetypes.python (4)
-- Patch L
I've seen similar too when I was using the GTK+ 3 build, though I never nailed
down how to reproduce it. I suspect something is not updated/synchronized after
a reload. IIRC it starts working again too once you switch tabs and back.
--
You are receiving this because you are subscribed to this t
OS: Arch Linux: "4.17.2-1-ARCH"
GTK 3.22.30, GLib 2.56.1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1893#issuecomment-403000117
Works for me.
What operating system, what versions of GTK and Glib (at the top of the
help->debug messages)?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1893#issuecomment-402972679
Geany version: 1.33
If the compilation of file A modifies file B, the scrollbar in file B doesn't
move after the compilation.
How to reproduce:
1. Start compilation of some file. It has to modify another opened file.
2. Switch to the other file that has been modified by the compilation.
3. In ap
As @codebrainz colourful exclamation indicates, macros are not expanded by the
inline parser. :)
So just looking at the line before the constructor, it is not valid C++, at
best it might parse as a function call, but with no semicolon between it and
the constructor the result is invalid C++, s
Lord almighty, the macroes! Just out of curiosity, what happens if you
pre-process that file using GCC `-E` argument and then open it in Geany?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/i
