minirst: support containers Text can be grouped into generic containers in reStructuredText: .. container:: foo This is text inside a "foo" container. .. container:: bar This is nested inside two containers. The minirst parser now recognizes these containers. The containers are either pruned completely from the output (included all nested blocks) or they are simply un-indented. So if 'foo' and 'bar' containers are kept, the above example will result in: This is text inside a "foo" container. This is nested inside two containers. If only 'foo' containers are kept, we get: This is text inside a "foo" container. No output is made if only 'bar' containers are kept. This feature will come in handy for implementing different levels of help output (e.g., verbose and debug level help texts).

     1

#!/bin/sh

     2

     3

mkdir test

     4

cd test

     5

echo foo>foo

     6

hg init

     7

hg addremove

     8

hg commit -m 1

     9

hg verify

    10

hg serve -p $HGPORT -d --pid-file=hg.pid

    11

cat hg.pid >> $DAEMON_PIDS

    12

cd ..

    13

    14

hg clone --pull http://localhost:$HGPORT/ copy | sed -e "s,:$HGPORT/,:\$HGPORT/,"

    15

cd copy

    16

hg verify

    17

hg co

    18

cat foo

    19

hg manifest --debug

    20

hg pull | sed -e "s,:$HGPORT/,:\$HGPORT/,"

    21

    22

echo % issue 622

    23

cd ..

    24

hg init empty

    25

cd empty

    26

hg pull -u ../test

    27

    28

echo % test file: uri handling

    29

hg pull -q file://../test-doesnt-exist

    30

hg pull -q file:../test

    31

hg pull -q file://foobar`pwd`/../test