-
Notifications
You must be signed in to change notification settings - Fork 28
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
Update config.rst #489
Update config.rst #489
Conversation
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.
It's a good change I think. Thanks @anton-seaice
I think we should put something in there about error handling to make it clear to users that a script or command that returns an error state can (and probably should) stop the model from running.
Now this doesn't have to happen in this PR, but it might make sense to do so.
Co-authored-by: Aidan Heerdegen <aidan.heerdegen@anu.edu.au>
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.
Thanks for fixing up the documentation!
Co-authored-by: Aidan Heerdegen <aidan.heerdegen@anu.edu.au>
Sorry I did the old trick of writing comments and then not clicking submit! ... See #489 (comment) |
I think this is ready to go now :) |
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.
Had a read through, and it looks good to me!
Thanks @jo-basevi ! |
Following on from #487 (comment)
Hopefully this clarifies how userscripts work (it will for me anyway :-) )