-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
grass.app: Move ISIS integration to the library #4169
Conversation
Path setup for ISIS was lost in GIS variable setup. This moves it to the library where other paths and integrations are initialized. This is untested. I'm leaving the variables as is.
@YannChemin I think you are the original author here. Do you want to take this opportunity to review the current state? |
@afrigeri please take a look as well. |
As far as the proposed code change, anyone please review and let's get this merged. I can get back to this when there are any followup changes proposed by @afrigeri or @YannChemin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why it was lost, but moving that same code around looks ok (inside a function).
Was the original function not always called when using new methods of starting grass in scripts?
Wow! Thanks @wenzeslaus and all |
With no other responses for the week, and the fact that I see @afrigeri 's thumbs up on last month's comment and his reponse, I'm moving this forward |
Path setup for ISIS was lost in GIS variable setup. This moves it to the library, where other paths and integrations are initialized. The variables are left as is, without further testing.
Path setup for ISIS was lost in GIS variable setup. This moves it to the library where other paths and integrations are initialized.
This is untested. I'm leaving the variables as is.