lima
Convert between
Haskell (.hs) files with GitHub-flavoured Markdown comments and Markdown (.md)
Literate Haskell (.lhs) files and GitHub-flavoured Markdown (.md).
It is usually possible to make conversion abide the roundtrip property. In other words, make conversions file.lhs -> file.lhs.md -> file.lhs.md.lhs or file.hs -> file.hs.md -> file.hs.md.hs and get file.lhs = file.lhs.md.lhs and file.hs = file.hs.md.hs in terms of their contents.
Alternatives
-
LiterateMarkdown. lima is a fork of this (abandoned?) project. Initially, I just wanted to fix some bugs, but then realized that I can't conveniently use Haskell Language Server with .lhs files so I added the .hs -> .md conversion.
-
IHaskell - create Jupyter notebooks with Haskell code cells and GitHub-flavoured Markdown text cells and do much more!
Conversion
hs <-> md
Examples
Rules:
- To produce text blocks, write multiline comments in
GitHub-flavoured Markdown
- Such comments should start with
{- or {-\n
- Multiline comments (even
{- -}) split Haskell code into snippets
- Special comments like
{- FOURMOLU_ENABLE -} won't appear in a .md. You can supply other comments in a config (hs-md.special-comments). See the sample config.
- You can ignore parts of a
.hs file by enclosing them into {- LIMA_DISABLE -} and {- LIMA_ENABLE -}. The lines between such comments will be commented out in the resulting .md.
- You can indent a Haskell snippet by writing a magic comment
{- LIMA_INDENT N -}, where N is an integer denoting the new indentation level. Reset the indentation by writing {- LIMA_DEDENT -}.
- If your snippet relates to some text, put the magic comment before that text
lhs <-> md
Examples:
Rules:
-
As .lhs doesn't support # (heading) or > (quotation start) at a line beginning, one should write # and > instead.
-
If you'd like to provide some code snippet in a .lhs, follow these rules:
> is for Haskell code, there should be an empty line before and after the block with Haskell code
< is for any other code. Such code will be converted into code blocks of type console in .md
- The round-trip property is not guarranteed if you insert code snippets into
.lhs using three backticks
- Nevertheless, feel free to insert them into
.md. In .lhs, they will just lose the language info
cabal
-
Clone this repo and install lima.
git clone https://github.com/deemp/flakes
cd flakes/lima
cabal update
cabal install .
nix
-
Install Nix
-
Get lima on PATH.
nix flake lock github:deemp/flakes
nix shell github:deemp/flakes?dir=lima
lima --help
Windows
To install the executable on Windows, if you can't convince cabal to use --bindir-method=copy you can build the project locally and copy the built executeable to C:/Users/username/AppData/Roaming/cabal/bin and ensure that this directory is in your PATH.
Contribute
Clone this repo and enter lima
git clone https://github.com/deemp/flakes
cd flakes/lima
cabal
Build as usually
cabal update
cabal build
nix
-
Install Nix. Optionally, learn more about Nix.
-
Run a devshell and build lima:
nix develop nix-dev/
cabal build
-
Optionally, start VSCodium:
nix run nix-dev/#writeSettings
nix run nix-dev/#codium .
-
Open a Haskell file there, hover over a term and wait until HLS shows the hints.
-
Troubleshoot if necessary.