This repository was archived by the owner on Jul 20, 2026. It is now read-only.
Write a user manual - #7
Draft
ISSOtm wants to merge 3 commits into
Draft
Conversation
It would be nice to have contextual keywords, but I guess those would be difficult.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1.
This is far from finished, but I'd like feedback on the form, tone, etc. before I start writing more.
The structure is kind of backwards, but like gb-asm-tutorial, it's impossible to talk about all of the details without overloading the reader, so I thought it best to paper over some things in the beginning.
Also, the "Writing scripts" chapter goes about some programming basics, but this is because I expect evscript to be usable and used by people who aren't usually programming. Hopefully that's fine with you?
Likewise, the organisation of the manual is subject to change: structure, content, ordering, chapter names... it's all up in the air, really.