v0.9.2
don't use tar --xform - it's not in bsd
feature-detect for sed flags across gnu/bsd

specifically, `sed -r` vs. `sed -E` for extended regexps, and different
argument patterns for `sed -i`.
sort --version-sort is not supported in bsd.

We used custom keys and the . delimiter to achieve the same effect.
Merge branch 'build.cross-platform'
hotfix for #164: don't parse 'oRZQ' like '\o\R\Z\Q'

see #164 for explanation
fix #180: couldn't type >1 spaces in RootTextBlock
'.end' => '.ends'

sed -i '' 's/\.end[[:>:]]/.ends/g' src/*.js

EXCEPT don't replace .end on Bracket's

Except for `.end` and `.endChild`, our convention has pretty
consistently been that collections are pluralized (e.g.  `LatexCmds`);
`.endChildren` is just such a mouthful though, so we're going with
`.ends` for both. They never conflict, `Fragment`s were the ones with
`first` and `last` and `Node`s were the ones with `{first,last}Child`,
and `node.ends[L]` can make sense as `node`'s leftmost child.

https://github.com/mathquill/mathquill/pull/160#issuecomment-16459573
'endChild' => 'ends'

sed -i '' 's/[[:<:]]endChild[[:>:]]/ends/g' src/*.js test/unit/*.js

Except for `.end` and `.endChild`, our convention has pretty
consistently been that collections are pluralized (e.g.  `LatexCmds`);
`.endChildren` is just such a mouthful though, so we're going with
`.ends` for both. They never conflict, `Fragment`s were the ones with
`first` and `last` and `Node`s were the ones with `{first,last}Child`,
and `node.ends[L]` can make sense as `node`'s leftmost child.

https://github.com/mathquill/mathquill/pull/160#issuecomment-16459573
use ` to mark variables in comment #cosmetic #comment
pull