patat: Terminal-based presentations using Pandoc

[ gpl, library, program, text ] [ Propose Tags ]

Terminal-based presentations using Pandoc


[Skip to Readme]

Flags

Manual Flags

NameDescriptionDefault
patat-make-man

Build the executable to generate the man page

Disabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.1.0.0, 0.2.0.0, 0.3.0.0, 0.3.1.0, 0.3.2.0, 0.3.3.0, 0.4.0.0, 0.4.2.0, 0.4.3.0, 0.4.4.0, 0.4.5.0, 0.4.6.0, 0.4.7.0, 0.4.7.1, 0.5.0.0, 0.5.1.0, 0.5.1.1, 0.5.1.2, 0.5.2.0, 0.5.2.1, 0.5.2.2, 0.6.0.0, 0.6.1.0, 0.6.1.1, 0.7.0.0, 0.7.2.0, 0.8.0.0, 0.8.1.1, 0.8.1.2, 0.8.1.3, 0.8.2.0, 0.8.2.1, 0.8.2.2, 0.8.2.3, 0.8.2.4, 0.8.2.5, 0.8.3.0, 0.8.4.0, 0.8.4.3, 0.8.5.0, 0.8.6.0, 0.8.6.1, 0.8.7.0, 0.8.8.0, 0.8.9.0, 0.9.0.0, 0.9.2.0, 0.10.0.0, 0.10.1.0, 0.10.1.1, 0.11.0.0, 0.12.0.0
Change log CHANGELOG.md
Dependencies aeson (>=0.9 && <1.4), ansi-terminal (>=0.6 && <0.9), ansi-wl-pprint (>=0.6 && <0.7), base (>=4.6 && <5), bytestring (>=0.10 && <0.11), containers (>=0.5 && <0.6), directory (>=1.2 && <1.4), filepath (>=1.4 && <1.5), mtl (>=2.2 && <2.3), network (>=2.6), network-uri (>=2.6), optparse-applicative (>=0.12 && <0.15), pandoc (>=2.0.4 && <2.3), semigroups (>=0.16 && <0.19), skylighting (>=0.1 && <0.8), terminal-size (>=0.3 && <0.4), text (>=1.2 && <1.3), time (>=1.6 && <1.10), unordered-containers (>=0.2 && <0.3), yaml (>=0.7 && <0.9) [details]
License GPL-2.0-only
Copyright 2016 Jasper Van der Jeugt
Author Jasper Van der Jeugt <m@jaspervdj.be>
Maintainer Jasper Van der Jeugt <m@jaspervdj.be>
Category Text
Home page http://github.com/jaspervdj/patat
Source repo head: git clone git://github.com/jaspervdj/patat.git
Uploaded by JasperVanDerJeugt at 2018-05-08T22:03:01Z
Distributions Debian:0.8.6.1, Fedora:0.9.2.0, NixOS:0.10.1.1
Reverse Dependencies 1 direct, 0 indirect [details]
Executables patat-make-man, patat
Downloads 25066 total (131 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
Last success reported on 2018-05-08 [all 3 reports]

Readme for patat-0.7.2.0

[back to package description]

patat

Build Status Hackage GitHub tag

patat (Presentations Atop The ANSI Terminal) is a small tool that allows you to show presentations using only an ANSI terminal. It does not require ncurses.

Features:

screenshot

Table of Contents

Installation

Pre-built-packages

You can also find generic linux binaries here: https://github.com/jaspervdj/patat/releases.

From source

Installation from source is very easy. You can build from source using stack install or cabal install. patat is also available from Hackage.

For people unfamiliar with the Haskell ecosystem, this means you can do either of the following:

Using stack

  1. Install stack for your platform.
  2. Clone this repository.
  3. Run stack setup (if you're running stack for the first time) and stack install.
  4. Make sure $HOME/.local/bin is in your $PATH.

Using cabal

  1. Install cabal for your platform.
  2. Run cabal install patat.
  3. Make sure $HOME/.cabal/bin is in your $PATH.

Running

patat [*options*] file

Options

-w, --watch

: If you provide the --watch flag, patat will watch the presentation file for changes and reload automatically. This is very useful when you are writing the presentation.

-f, --force

: Run the presentation even if the terminal claims it does not support ANSI features.

-d, --dump

: Just dump all the slides to stdout. This is useful for debugging.

--version

: Display version information.

Controls

  • Next slide: space, enter, l, , PageDown
  • Previous slide: backspace, h, , PageUp
  • Go forward 10 slides: j,
  • Go backward 10 slides: k,
  • First slide: 0
  • Last slide: G
  • Reload file: r
  • Quit: q

The r key is very useful since it allows you to preview your slides while you are writing them. You can also use this to fix artifacts when the terminal is resized.

Input format

The input format can be anything that Pandoc supports. Plain markdown is usually the most simple solution:

---
title: This is my presentation
author: Jane Doe
...

# This is a slide

Slide contents.  Yay.

---

# Important title

Things I like:

- Markdown
- Haskell
- Pandoc

Horizontal rulers (---) are used to split slides.

However, if you prefer not use these since they are a bit intrusive in the markdown, you can also start every slide with a header. In that case, the file should not contain a single horizontal ruler.

patat will pick the most deeply nested header (e.g. h2) as the marker for a new slide. Headers above the most deeply nested header (e.g. h1) will turn into title slides, which are displayed as as a slide containing only the centered title.

This means the following document is equivalent to the one we saw before:

---
title: This is my presentation
author: Jane Doe
...

# This is a slide

Slide contents.  Yay.

# Important title

Things I like:

- Markdown
- Haskell
- Pandoc

And that following document contains three slides: a title slide, followed by two content slides.

---
title: This is my presentation
author: Jane Doe
...

# Chapter 1

## This is a slide

Slide contents.  Yay.

## Another slide

Things I like:

- Markdown
- Haskell
- Pandoc

For more information, see Advanced slide splitting.

Patat supports comments which can be used as speaker notes.

---
title: This is my presentation
author: Jane Doe
...

# Chapter 1

<!--
Note: I should not bore the audience with my thoughts on powerpoint but
just get straight to the point.
-->

Slide contents.  Yay.

<!-- TODO: Finish the rest of the presentation. -->

Configuration

patat is fairly configurable. The configuration is done using YAML. There are two places where you can put your configuration:

  1. In the presentation file itself, using the Pandoc metadata header.
  2. In $HOME/.patat.yaml

For example, we set an option key to val by using the following file:

---
title: Presentation with options
author: John Doe
patat:
    key: val
...

Hello world.

Or we can use a normal presentation and have the following $HOME/.patat.yaml:

key: val

Line wrapping

Line wrapping can be enabled by setting wrap: true in the configuration. This will re-wrap all lines to fit the terminal width better.

Auto advancing

By setting autoAdvanceDelay to a number of seconds, patat will automatically advance to the next slide.

---
title: Auto-advance, yes please
author: John Doe
patat:
    autoAdvanceDelay: 2
...

Hello World!

---

This slide will be shown two seconds after the presentation starts.

Note that changes to autoAdvanceDelay are not picked up automatically if you are running patat --watch. This requires restarting patat.

Advanced slide splitting

You can control the way slide splitting works by setting the slideLevel variable. This variable defaults to the least header that occurs before a non-header, but it can also be explicitly defined. For example, in the following document, the slideLevel defaults to 2:

# This is a slide

## This is a nested header

This is some content

With slideLevel 2, the h1 will turn into a "title slide", and the h2 will be displayed at the top of the second slide. We can customize this by setting slideLevel manually:

---
patat:
  slideLevel: 1
...

# This is a slide

## This is a nested header

This is some content

Now, we will only see one slide, which contains a nested header.

Fragmented slides

By default, slides are always displayed "all at once". If you want to display them fragment by fragment, there are two ways to do that. The most common case is that lists should be displayed incrementally.

This can be configured by settings incrementalLists to true in the metadata block:

---
title: Presentation with incremental lists
author: John Doe
patat:
    incrementalLists: true
...

- This list
- is displayed
- item by item

Setting incrementalLists works on all lists in the presentation. To flip the setting for a specific list, wrap it in a block quote. This will make the list incremental if incrementalLists is not set, and it will display the list all at once if incrementalLists is set to true.

This example contains a sublist which is also displayed incrementally, and then a sublist which is displayed all at once (by merit of the block quote).

---
title: Presentation with incremental lists
author: John Doe
patat:
    incrementalLists: true
...

- This list
- is displayed

    * item
    * by item

- Or sometimes

    > * all at
    > * once

Another way to break up slides is to use a pagraph only containing three dots separated by spaces. For example, this slide has two pauses:

Legen

. . .

wait for it

. . .

Dary!

Theming

Colors and other properties can also be changed using this configuration. For example, we can have:

---
author: 'Jasper Van der Jeugt'
title: 'This is a test'
patat:
    wrap: true
    theme:
        emph: [vividBlue, onVividBlack, bold]
        imageTarget: [onDullWhite, vividRed]
...

# This is a presentation

This is _emph_ text.

![Hello](foo.png)

The properties that can be given a list of styles are:

blockQuote, borders, bulletList, codeBlock, code, definitionList, definitionTerm, emph, header, imageTarget, imageText, linkTarget, linkText, math, orderedList, quoted, strikeout, strong, tableHeader, tableSeparator

The accepted styles are:

bold, dullBlack, dullBlue, dullCyan, dullGreen, dullMagenta, dullRed, dullWhite, dullYellow, onDullBlack, onDullBlue, onDullCyan, onDullGreen, onDullMagenta, onDullRed, onDullWhite, onDullYellow, onVividBlack, onVividBlue, onVividCyan, onVividGreen, onVividMagenta, onVividRed, onVividWhite, onVividYellow, underline, vividBlack, vividBlue, vividCyan, vividGreen, vividMagenta, vividRed, vividWhite, vividYellow

Syntax Highlighting

As part of theming, syntax highlighting is also configurable. This can be configured like this:

---
patat:
  theme:
    syntaxHighlighting:
      decVal: [bold, onDullRed]
...

...

decVal refers to "decimal values". This is known as a "token type". For a full list of token types, see this list -- the names are derived from there in an obvious way.

Pandoc Extensions

Pandoc comes with a fair number of extensions on top of markdown:

<https://hackage.haskell.org/package/pandoc-2.0.5/docs/Text-Pandoc-Extensions.html>

patat enables a number of them by default, but this is also customizable.

In order to enable an additional extensions, e.g. autolink_bare_uris, add it to the pandocExtensions field in the YAML metadata:

---
patat:
  pandocExtensions:
    - patat_extensions
    - autolink_bare_uris
...

Document content...

The patat_extensions in the above snippet refers to the default set of extensions enabled by patat. If you want to disable those and only use a select few extensions, simply leave it out and choose your own:

---
patat:
  pandocExtensions:
    - autolink_bare_uris
    - emoji
...

...

Document content...

If you don't want to enable any extensions, simply set pandocExtensions to the empty list [].

Trivia

"Patat" is the Flemish word for a simple potato. Dutch people also use it to refer to French Fries but I don't really do that -- in Belgium we just call fries "Frieten".

The idea of patat is largely based upon MDP which is in turn based upon VTMC. I wanted to write a clone using Pandoc because I ran into a markdown parsing bug in MDP which I could not work around. A second reason to do a Pandoc-based tool was that I would be able to use Literate Haskell as well. Lastly, I also prefer not to install Node.js on my machine if I can avoid it.