nitasema  Check-in [0d977d116f]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:more markup fixes
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | trunk
Files: files | file ages | folders
SHA3-256: 0d977d116f426a3cfd4797d4bbed9e4158aeda23f9ac082c49a992e9cea1418c
User & Date: lexi 2019-04-28 04:39:29
Context
2019-04-28
04:39
more markup fixes Leaf check-in: 0d977d116f user: lexi tags: trunk
04:17
fix readme check-in: 48d289b8b2 user: lexi tags: trunk
Changes

Changes to README.md.

12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
## file format
the nitasema \*.n file format is based on simplified s-exps. it is designed primarily as an intermediate format for a forthcoming GUI editor but in the meantime it's perfectly intelligible to humans to and only slightly verbose.

lines can be commented out with the `;` character. there are currently no multiline comments.

whitespace is used to delimit values and is otherwise insignificant.

the data types are atoms, strings, and lists. strings are delimited by single-quotes (`'`) and can span any number of lines. lists are delimited by `[` and `]` (not the more usual parentheses, for ease of typing). atoms may contain any character in the ascii range '-' ~ 'z' | 'A' ~ 'Z' and any unicode character outside the ascii range. backslash (`\\`) can escape single quotes in a string.

the first term in the \*.n file must be a string naming the story. it may be followed by atoms to mark various flags.

### flags
* `by`: sets the author. takes a string argument. currently has no effect on output. (`by 'alexis hale'`)
* `flags`: declares booleans. must be followed by a list of booleans. (`flags [bloodsoaked screaming bleeding]`)
* `vars`: declares variables. must be followed by a list of variables. (`vars [health sanity terror]`)







|







12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
## file format
the nitasema \*.n file format is based on simplified s-exps. it is designed primarily as an intermediate format for a forthcoming GUI editor but in the meantime it's perfectly intelligible to humans to and only slightly verbose.

lines can be commented out with the `;` character. there are currently no multiline comments.

whitespace is used to delimit values and is otherwise insignificant.

the data types are atoms, strings, and lists. strings are delimited by single-quotes (`'`) and can span any number of lines. lists are delimited by `[` and `]` (not the more usual parentheses, for ease of typing). atoms may contain any character in the ascii range '-' ~ 'z' \| 'A' ~ 'Z' and any unicode character outside the ascii range. backslash (`\\`) can escape single quotes in a string.

the first term in the \*.n file must be a string naming the story. it may be followed by atoms to mark various flags.

### flags
* `by`: sets the author. takes a string argument. currently has no effect on output. (`by 'alexis hale'`)
* `flags`: declares booleans. must be followed by a list of booleans. (`flags [bloodsoaked screaming bleeding]`)
* `vars`: declares variables. must be followed by a list of variables. (`vars [health sanity terror]`)