From 8c8972b7498eb8a864b34df3de6558fb4064ae0d Mon Sep 17 00:00:00 2001 From: Lars-Dominik Braun Date: Sun, 1 Apr 2018 20:12:45 +0200 Subject: Support Pandoc 2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Apparently the new major release broke its public API, but – thankfully – added support for RST’s include directive. --- src/Codec/Pesto.lhs | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) (limited to 'src/Codec/Pesto.lhs') diff --git a/src/Codec/Pesto.lhs b/src/Codec/Pesto.lhs index cf20105..5637059 100644 --- a/src/Codec/Pesto.lhs +++ b/src/Codec/Pesto.lhs @@ -18,13 +18,17 @@ About this document ------------------- This section contains various information about this document. The `second -section `_ motivates why inventing another file format is -necessary, followed by the goals_ of Pesto. After a short Pesto `primer -`_ intended for the casual user the language’s -`syntax `_ and `semantics `_ are -presented. The `linting section `_ limits the language to useful -cooking recipes. Examples for user presentation of recipes and serialization -follow. +section`__ motivates why inventing another file format is necessary, followed +by the goals_ of Pesto. After a short Pesto primer__ intended for the casual +user the language’s syntax__ and semantics__ are presented. The `linting +section`__ limits the language to useful cooking recipes. Examples for user +presentation of recipes and serialization follow. + +__ motivation_ +__ introduction-by-example_ +__ language-syntax_ +__ language-semantics_ +__ linting_ Being a literate program this document is specification and reference implementation at the same time. The code is written in Haskell_ and uses the @@ -217,6 +221,8 @@ maintained in a separate database. Due to its minimal syntax Pesto is also not suitable for extensive guides on cooking or the usual chitchat found in cooking books. +.. _introduction-by-example: + Introduction by example ----------------------- -- cgit v1.2.3