mmtpygments 0.3.6

Pygments plugin for MMT surface syntax (lexer & style)

   | GitHub Repo | Collection of rendered codes

mmtpygments: Pygments plugin for MMT surface syntax

To support syntax highlighting of the MMT Surface Syntax from the MMT project this package is a Pygments plugin including

• a Pygments lexer (mmt)
• a recommended Pygments style for it (mmtdefault)
• and experimentally a Pygments lexer for MMT relational data (mmtrel).

Collection of rendered codes: click here
Screenshot: (click for live version)

Installation

Via Pip (recommended)

1. pip install Pygments mmtpygments

2. Use as you wish with Pygments, e.g. run on CLI:

   pygmentize -f html -l mmt -O full,style=mmtdefault -o test.html test.mmt

   This tells Pygments to use the HTML formatter (-f), the MMT lexer (-l) and to output a full HTML file using the mmtdefault style (-O) rendered of test.mmt into test.html (-o).

Usage in LaTeX with minted

minted is a LaTeX package rendering codes with Pygments as the backend.

% !TEX TS-program = latexmk -xelatex -shell-escape -silent -latexoption="-synctex=1 -8bit" %

% ^^^ This is the build command. Install latexmk if you don't have it already.
%     You may choose an alternative LaTeX derivative, e.g. LuaLaTeX, but be warned that it must support Unicode!
%
%     Let your IDE run this build command (or run it manually) in an "PATH environment", where
%       (1) `python` is available as a command and
%       (2) you installed the Pip packages `pygments` and `mmtpygments`.
%
%     The easiest way is to just install Python on your computer and run `pip install pygments mmtpygments`.
%
%     A better way would be to
%       (1) install Python on your computer,
%       (2) run `pip install pipenv`,
%       (3) and then in your directory for this TeX document run:
%         (3.1) `pipenv install pygments mmtpygments`
%         (3.2) `pipenv shell`
%
%     Now start the build command or your IDE from this very shell. This way, you don't clutter
%     your whole PC with the Pip packages *and* more importantly, you document the Pip package
%     versions in the `Pipfile.lock` file generated in step (2.1).


\documentclass{article}

\usepackage{fontspec}

% Download GNU Unifont from http://unifoundry.com/unifont/index.html
% And save it, say, as "fonts/unifont-12.1.03.ttf"
\newfontfamily\unifont{unifont-12.1.03.ttf}[Path=./fonts/,NFSSFamily=unifont]

% Disable caching for debugging purposes (increases compilation times!)
\usepackage[cache=false]{minted}
\setminted{
	fontfamily=unifont
}

\newminted[mmtcode]{mmt}{}
\newmintinline[mmtinline]{mmt}{}
\newmintedfile[mmtfile]{mmt}{}

\begin{document}
	% Variant 1: Code given in LaTeX, rendered in display mode
	\begin{mmtcode}
theory MyTheory = c : type ❘ # abc ❙❚
	\end{mmtcode}

	% Variant 2: Code given in LaTeX, rendered inline
	% You can use any delimiter you like, here we use /
	\mmtinline/theory MyTheory = c : type ❘ # abc ❙❚/

	% Variant 3: Code given externally in file, rendered in display mode
	% \mmtfile{your-mmt-file.mmt}
\end{document}

LaTeX Beamer: Use the fragile option for frames embedding codes: \begin{frame}[fragile] ... \end{frame}

See the minted manual for more information on how to customize it.

Common Error: Rendered PDF shows tab characters of source

If you tab characters in the MMT source being highlighted and they are shown in the PDF rendered by XeLaTeX, you face a known bug of XeLaTeX ([1], [2]). It can be solved by passing -8bit to XeLaTeX.

Development

1. Install pipenv, which provides a consistent Python, pip and package environment locked in the committed Pipfile and Pipfile.lock files.
2. pipenv install
3. git submodule init
4. git submodule update

Testing

1. cd mmtpygments/test
2. pipenv run python test.py ./ (returns non-zero exit code on failure)
3. Open index.html in a browser to see failures visually (red rectangles).

This test.py runs the lexer on large MMT archives containing a lot of MMT surface syntax. It recursively searches for MMT files in mmtpygments/test/data, on which it then runs the provided lexer and Pygment's HtmlFormatter. The rendered versions are written next to the original *.mmt files with an .html extension. Furthermore, index.html and amalgamation.html are generated to link and display the results, respectively.

The Travis build automatically runs test.py and deploys the results on the gh-pages branch, see https://comfreek.github.io/mmtpygments/ and especially https://comfreek.github.io/mmtpygments/mmtpygments/test/index.html.

Development

For tinkering and testing the lexer, it is recommended to employ the same testing infrastructure as described above. Even though the Travis build fails on lexing error, test.py actually doesn't -- it just returns a non-zero exit code. In fact, it even generates the HTML renderings with red rectangles around lexing errors. Hence, while tinkering with the lexer, just regularly run test.py and look at the index.html locally in your browser to see any errors.

Publishing

Publishing is done automatically via .travis.yml upon tagged commits on the master branch. For that do

1. Locally commit all your changes.
2. Create a new version tag: git tag -a vx.y.z -m "Version x.y.z, see CHANGELOG.md" (the tag name needs to start with v and a digit for Travis CI to pick it up, see .travis.yml)
3. Push the commit and the tag: git push && git push --tags

Not recommended: If you really have to publish a version manually for whatever reason, do the following:

# Packaging
$ pipenv run python setup.py sdist bdist_wheel

# Checking if packages are okay (PyPi server will do the same)
$ pipenv run twine check dist/*

# Upload to Test PyPi repository
$ pipenv run twine upload --repository-url https://test.pypi.org/legacy/ dist/*

# Upload to real PyPi repository
$ pipenv run twine upload dist/*

For future maintainers: necessary changes in case of repository movement

In case you wish to host this repository or a fork thereof somewhere else, these are the places where you have to make changes:

• README.md: Change all links referencing anything under https://ComFreek.github.io/mmtpygments to the URI where you deploy your things.
• .travis.yml:
  • Change the base path with which python test.py is run to your hosting URI.
  • Change the secret value in under deploy/pypi to another PyPI token under which you are able to publish PyPI packages.