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

geanyminiscript: Drop use of the most obvious deprecated Geany API #360

Merged
merged 2 commits into from
Jun 9, 2016

Conversation

b4n
Copy link
Member

@b4n b4n commented Feb 21, 2016

Not tested.

@earshinov

@b4n
Copy link
Member Author

b4n commented Mar 3, 2016

I just added a commit not to access private Geany fields, as pointed out in geany/geany#910

This slightly changes the behavior as it will now follow the setting
from the project open at startup, if any.  It's however probably rather
an improvement, although caching the value is likely not to be a good
idea anyway.
@b4n b4n force-pushed the geanyminiscript/less-deprecated branch from 22a9970 to e09f539 Compare March 3, 2016 16:31
@frlan frlan added this to the 1.28 milestone Mar 13, 2016
@techee techee merged commit 048c1e1 into geany:master Jun 9, 2016
@techee
Copy link
Member

techee commented Jun 9, 2016

LGBI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants