Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS Catalina: Geany 1.36 code editor display issue #2413

Closed
ckataki opened this issue Jan 1, 2020 · 8 comments
Closed

MacOS Catalina: Geany 1.36 code editor display issue #2413

ckataki opened this issue Jan 1, 2020 · 8 comments
Assignees
Labels

Comments

@ckataki
Copy link

ckataki commented Jan 1, 2020

Using Geany on Mac has display issues in the code editor. Using v1.36 with standard plugins, and no custom configuration, and MacOS Catalina. Moving the cursor around in the editor messes up the lines displayed (see gif to get a better idea, look at the line numbers). A couple of scrolls up and down fixes it for a while. As far as I can tell, it's just a display issue, since if I start typing, text gets entered at the line the cursor is supposed to be at.

The file is a small 120 line file; another ~200 line file is open in another editor tab.

Screen Recording 2020-01-01 at 14 51 54

@elextr elextr added the macos label Jan 1, 2020
@ckataki
Copy link
Author

ckataki commented Jan 14, 2020

FYI, I only see this after the Catalina upgrade. This doesn't seem to be an issue on earlier MacOS versions.

@motorkap
Copy link

motorkap commented Feb 12, 2020

Hi there, I also experienced this issue (Catalina 10.15.2, Geany 1.36). I have replaced my Geany with the version available here (n.b. the file name is the same as my original install but the contents are different...).

Its early days yet but I have scrolled around in some files that were problematic and the issue seems to have disappeared.

I found this download via the issue discussion here. That issue is on the face of it unrelated but fixing the screen painting seems to be a welcome side effect .

Hope this helps!

BTW, since posting the above I found this. It seems to be the same or very similar issue and proposes the same fix (the new download has moved to GTK3).

@techee
Copy link
Member

techee commented Feb 16, 2020

@b4n It seems many people are running into the problem so maybe I should make a new mac-only release and put it into downloads instead of snapshots where it's hard to find. How should I name the dmg file? Technically it won't be 1.36.1 because there's no such Geany release.

@motorkap
Copy link

I see the problem, your numbering scheme doesn't really lend itself to divergence on a per-platform basis. I wouldn't beat yourself up about this as there is no obvious elegant solution (as far as I can see). The important thing is that users can distinguish between the two functionally equivalent 1.36 versions.

You could introduce a 4th digit group for patch level, i.e. go to 1.36.0.1 on mac. Or you could introduce some kind of suffix (like rc1 for release candidate1, fp1 (fix pack1), dr1 (defect resolution) or just the more neutral upd1 for update).

How about geany-1.36_osx_upd1.dmg ?

@elextr
Copy link
Member

elextr commented Feb 17, 2020

The problem here IIUC is that the osx build adds stuff to the basic geany, so changes to the osx stuff don't affect Geany itself and its version number. Perhaps the osx (and windows?) builds need to be themselves versioned so geany-1.36_osx-2.dmg? This is similar to the Debian/Ubuntu habit of adding -n to a package for the version of their build.

@b4n
Copy link
Member

b4n commented Feb 17, 2020

@techee I agree with @elextr, a OSX-specific version suffix sounds pretty good to me.

@motorkap
Copy link

I also vote for the suggestion from @elextr. I'm all for simplicity and adoption (or mimicking) existing conventions.

@techee
Copy link
Member

techee commented Mar 22, 2020

Done (finally). You can now download the latest macOS Geany from the downloads page. I've also used the latest GTK 3 version which fixes some problems that were present in the previous snapshot.

@techee techee closed this as completed Mar 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants