Files
ioccc/2015/endoh2
Landon Curt Noll a9ca93ec47 fix markdown footnote problem caused by pandoc
Add "<!-- BEFORE: 1st line of markdown file: FILE/PATH -->"
before the markdown content.  This line appears in the
generated HTML.

Add "<!-- AFTER: last line of markdown file: FILE/PATH -->"
after the markdown content.  This line appears in the
generated HTML.

We test a fix relating to problems produced by `pandoc(1)`
when footnotes are added at the end of generated HTML.
This test is made for `2000/bmeyer/index.html`.

Fixed exit 4 in `bin/md2html.sh that should be exit 5.

Changed `bin/md2html.sh` VERSION from to "1.3 2024-04-14"
to "1.4 2024-04-18".

Run `bin/readme2index.sh -v 1 2000/bmeyer` to perform the above.
2024-04-19 01:20:31 -07:00
..
2024-03-13 00:38:46 -07:00
2020-12-30 16:57:03 -08:00
2023-07-06 21:49:38 -07:00

To build:

    make

To use:

    ./prog

Try:

    ./try.sh

Judges' remarks:

At this point you might be wondering, WTF?*

  • What The Freak (polite form)

  • What's This For? (you may be wondering)

  • What the Fish (python form)

How is this code obfuscated? Well look again:

    less prog.c

    more prog.c

Where did those underscores come from? Well RTFS!**

** Read the Freaking Source (polite form) ** Read The Freaking Screen (polite form)

If you are still puzzled, look at prog.c with your favorite text editor.

Author's remarks:

Follow these instructions literally!

    cat prog.c
    gcc -w -o prog prog.c
    ./prog

You will do a double take.

Hint 1: Do less prog.c. You will see an emphasized string if your terminal supports bold.

Hint 2: Do wc -c prog.c. This is very long one-liner.

Spoiler: Open the source with an editor like vim or emacs.