fsh/doc/esoterica

If you're not developing,
this is just technobabble.

If you are planning to develop,
seriously grok these docs for an easier experience.

Format

Code goes in backtics (SHIFT+tilde on a QWERTY keyboard),
parameters go inside angle brackets <like/> <so/>(, parentheses used to indicate optional segments).

blocks use #instruction#;bashcode;#noitcurtsni# nomenclature, eg:

#setup#
mkdir -p $(realpath ~/)project/fsh
#putes#

This allows us to parse looking for lines that both end & begin with a hashmark, and then pattern match the inverted string against future similarly-bookended lines (probably using perl because speed)

Conditionals

Dependencies can be met in more than one way.

GCC:4.9||Clang:3.5
and
apt||apt-get
are both examples of this.

Security

Bash has nuance, and the pitfalls are many & varied, listen to someone competent on the subject (*).

Safe is fast, y'all.