skylighting VS arx

If anyone wants to try this, the file is here: https://github.com/jgm/skylighting/blob/master/skylighting-core/xml/haskell.xml

2) Pandoc invokes the skylight Haskell library, which uses XML syntax descriptions to define which tokens/pieces of a given language have which "role". Skylight will parse your code and tag each part of it according to those rules. You can edit those XML files (or create new ones). Check this page for a description of how they work. You'll find the existing KDE XML syntax descriptors here.

For those wanting to go down the self-extracting executable route, I recommend arx (it generates that sort of tarball-prepended-with-shell-script you describe) https://github.com/solidsnack/arx

The `nix bundle` command can generate an arx file, which includes all of an application's dependencies. As an example, we started getting issues with an EC2 server whose image was an accumulation of changes over several years; whilst we worked on migrating to a saner setup (containers defined using Nix), as a stop-gap we got the server working again by using `nix bundle` to create an arx executable containing working versions of all the application's dependencies, which we could copy to the existing server as a drop-in replacement of the existing (broken) command.