Misc title with an inline html export

neato!

see ./headlines.org

Note that only src/example/export block inclusion is supported for now. There's quite a lot more to include (see the org manual for include files) but I don't have a use case for this yet and stuff like namespacing footnotes of included files adds quite a bit of complexity.

for now files can be included as:

• src block

  #+SETUPFILE: setup_file_org
  #+OPTIONS: toc:1
  * Simple Headline [1/2]
  - [X] checked
  - [ ] unchecked
  - note that statistic tokens are marked up anywhere
    not just where they are actually meant to be - even here > [100%] <
    (Org mode proper does the same)
  * TODO [#B] Headline with todo status & priority
  * DONE Headline with TODO status
  :PROPERTIES:
  :custom_id: this-will-be-the-id-of-the-headline
  :note: property drawers are not exported as html like other drawers
  :END:
  
  we can link to headlines that define a custom_id: [[#this-will-be-the-id-of-the-headline]]
  * [#A] Headline with tags & priority                                :foo:bar:
  Still outside the drawer
  :DRAWERNAME:
  This is inside the drawer
  :end:
  Still outside the drawer
  * CUSTOM headline with custom status
  it's possible to use =#+SETUPFILE= - in this case the setup file contains the following
  
  #+INCLUDE: "setup_file_org" src org
  * excluded headline                                                :custom_noexport:
  this headline and it's content are not exported as it is marked with an =EXCLUDE_TAGS= tag.
  By default =EXCLUDE_TAGS= is just =:noexport:=.
  
  * TODO [#A] COMMENT commented headline
  this headline is commented out. see [[https://orgmode.org/manual/Comment-Lines.html][comment lines]]
  * malformed property drawer
  :PROPERTIES:
  not a property
  :END:
  * level limit for headlines to be included in the table of contents
  The toc option allows setting a [[https://orgmode.org/manual/Export-settings.html][level limit]]. For this file we set it to 1 - which means that the following headlines
  won't be included in the table of contents.
  ** headline 2 not in toc
  *** headline 3 not in toc
  ** anoter headline 2 not in toc
  you get the gist...
  

• export block

  Paragraphs are the default element.

  Empty lines and other elements end paragraphs - but paragraphs can obviously span multiple lines.

  Paragraphs can contain inline markup like emphasis strong and links example.com and stuff.

• example block

  name: CI
  
  on:
    push:
      branches: [ master ]
  
  jobs:
    build:
      runs-on: ubuntu-latest
      steps:
      - name: git
        run: |
          git clone --depth 1 "https://x-access-token:${{secrets.GITHUB_TOKEN}}@github.com/${GITHUB_REPOSITORY}" .
          git config user.name "GitHub Action"
          git config user.email "action@github.com"
          git log -1 --format="%H"
      - name: go
        run: sudo snap install go --classic
      - name: test
        run: make test
      - name: gh-pages
        run: |
          git checkout --orphan gh-pages && git reset
          make generate-gh-pages
          git add -f docs/ && git commit -m deploy
          git push -f origin gh-pages
      - name: notify
        if: ${{ failure() }}
        run: |
          text="https://github.com/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID} failed"
          curl --silent --output /dev/null ${{secrets.TELEGRAM_URL}} -d "chat_id=${{secrets.TELEGRAM_CHAT_ID}}&text=${text}"
  

• ndash –
• mdash —
• ellipsis …
• acute Á and so on
• note that —— is replaced with 2 mdashes and …. becomes ellipsis+. and so on - that's how org also does it

either this or that foo. either this or that foo.

• this list item has multiple linbreaks - but it's still just one paragraph (i.e. no line breaks are rendered)
• foobar

1. same goes for ordered lists
2. foo

this is markup!

• bullet 1

  • sub bullet

italics

Text italics

just like #46

• -- -> – (en dash)
• --- -> — (em dash)

also, consecutive dashes inside

• inline code -- --- and verbatim -- ---

• src/example/export blocks should not be converted!

  --, ---
  

  --, ---
  

  --, ---

  --, ---
  

footnotes can contain markup - and other elements and stuff ^{1 2}

The behaviour of Org mode <s TAB changed and it now inserts lowercased src blocks (go-org already handled this one)

• lowercased:

  uname -a
  

• uppercased

  uname -a
  

Hello, I'm writing hugo blogs using org-mode.

When inserting an image link like , hugo doesn't export the image.

0\\

• a list item