Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/abeleinin/papyrus
📜 Papyrus: Pandoc integration for automatic file conversion in Vim!
https://github.com/abeleinin/papyrus
latex markdown markdown-to-pdf neovim neovim-plugin pandoc vim vim-plugin
Last synced: 8 days ago
JSON representation
📜 Papyrus: Pandoc integration for automatic file conversion in Vim!
- Host: GitHub
- URL: https://github.com/abeleinin/papyrus
- Owner: abeleinin
- License: mit
- Created: 2023-02-15T23:44:15.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-07-07T06:26:22.000Z (over 1 year ago)
- Last Synced: 2024-08-01T16:56:22.845Z (3 months ago)
- Topics: latex, markdown, markdown-to-pdf, neovim, neovim-plugin, pandoc, vim, vim-plugin
- Language: Vim Script
- Homepage:
- Size: 4.73 MB
- Stars: 64
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Papyrus
Automatically compile Markdown notes into beautiful Latex PDFs or other supported pandoc formats!
Theme: [material default-community](https://github.com/kaicataldo/material.vim)
Papyrus is an asynchronous Markdown conversion plugin that allows users to have a latex-like editing experience while writing Markdown. By utilizing the [Pandoc](https://pandoc.org/) universal document converter you can write Markdown and Latex syntax in the same file and convert it into a PDF or other Pandoc supported document types.
**Features**
- Asynchronous compilation
- Ability to set custom Pandoc command-line arguments
- Optional templates
## Table of contents
- [Requirements](#requirements)
- [Installation](#installation)
- [Configuration](#configuration)
- [Errors Messages](#error-messages)
- [Commands](#commands)
- [Documentation](#documentation)
- [Images](#images)
- [Fonts](#fonts)
- [Templates](#templates)
- [Demo](#demo)
## Requirements
- [Pandoc](https://pandoc.org/installing.html)
- [Latex Engine](https://pandoc.org/MANUAL.html#option--pdf-engine)
Supported Engines: pdflatex, lualatex, xelatex, latexmk, tectonic, wkhtmltopdf, weasyprint, pagedjs-cli, prince, context, and pdfroff.
## Installation
### Vim Plugin
Add the following to your `.vimrc` or `init.vim` file to install the plugin using a plugin manager of your choice. Here are some examples:
```vim
" vim-plug
Plug 'abeleinin/papyrus'
" packer.nvim
use 'abeleinin/papyrus'
" vundle
Plugin 'abeleinin/papyrus'
```
I *strongly* recommend also installing the [vim-pandoc-syntax](https://github.com/vim-pandoc/vim-pandoc-syntax) plugin to visualize Latex special characters.
### Pandoc Templates
**Templates are optional**
Move the Latex template files from wherever your plugin is installed (`~/papyrus/templates/latex/*`) to the pandoc templates folder. The pandoc template folder depends on the OS you're using:
- Unix, Linux, macOS: `$HOME/.local/share/pandoc/templates` or `$HOME/.pandoc/templates`
- Windows: `C:\$HOME\AppData\Roaming\pandoc\templates`
If the `templates` or `pandoc` folder doesn't exist then you need to create them and put the template files into the new directory. You can also find the default *User data directory* by checking `pandoc --version`.
## Configuration
After installation, copy the following configurations into your `.vimrc` or `init.vim` file to configure Papyrus to your specification.
```vim
" Specify a Latex Engine from the supported list above
let g:papyrus_latex_engine = 'xelatex'
" Specify any built-in pdf viewing option. It's recommended to use
" a pdf viewer with automatic updates on save.
let g:papyrus_viewer = 'zathura'
" Recommended keybinding for compiling and viewing documents
" Adding optional formattings is also possible by
map pc :PapyrusCompile
map pa :PapyrusAutoCompile
map pv :PapyrusView
map ps :PapyrusStart
```
### Optional
`g:papyrus_pandoc_args`: Add custom [pandoc compilation](https://pandoc.org/MANUAL.html#general-writer-options) arguments.
`g:papyrus_autocompile`: Default set to `BufWrite` alternative [autocmd events](https://neovim.io/doc/user/autocmd.html#autocmd-events) can be used to trigger auto-compilation.
`g:papyrus_output_path`: Set a custom output folder path in the format `/path/to/folder/`. Do not include `$HOME` or `~`.
`g:papyrus_output_format`: Default output format is set to `pdf` which can be changed to any supported pandoc output format which is listed when running `pandoc --list-output-formats`.
`g:papyrus_template`: Set a template from supported options.
### Customization
If a command has an [optional argument](#commands) you can add custom mappings for different compilation formats. For example:
```vim
" Compile current file to pdf
map pcp :PapyrusCompile pdf
" Compile current file to html
map pch :PapyrusCompile html
```
## Error Messages
After every compilation either the message `Papyrus: Compilation Succeeded!` will appear at the bottom of the window or `Papyrus: Compilation Failed with exit status X`. After a failed compilation the **pandoc compilation errors are displayed in a quickfix list** which can be viewed using `:copen`.
## Commands
**Optional arguments** allow you to change the current file output format. Possible output formats are listed when running `pandoc --list-output-formats`.
### :PapyrusCompile \
Executes a `pandoc` command using `jobstart` to compile the current open `md` file into a `pdf` with the same name using either the `g:papyrus_pandoc_args` or `g:papyrus_template`.
### :PapyrusAutoCompile \
Executes an `autocmd` when the `g:papyrus_autocompile` event is triggered which runs `:PapyrusCompile`.
### :PapyrusView
Opens the current file in the specified pdf viewer from the `g:papyrus_viewer` variable.
### :PapyrusStart \
Runs `:PapyrusView` and `:PapyrusAutoCompile` to automatically start an editing environment.
### :PapyrusHeader
Copies the specified template file into the current file from `/templates/md/g:papyrus_template`.
### :PapyrusNew
Runs `:PapyrusHeader` and `:PapyrusStart` to create a new editing environment for the specified template.
## Documentation
### Images
```md
# Insert image from current directory
# Add figure caption
# Insert images from different directory
# Append {width="50%"} to adjust dimensions
{width="50%"}
```
### Fonts
To add custom fonts you first need to verify that the font is downloaded to your systems. For example, on Mac, you can use the Font Book application to add any font from the internet. There are two ways to specify a font using Papyrus. First, you can use the mainfont variable in the YAML heading at the top of your markdown document:
```yaml
---
title: Custom Font
author: Author
date: xx-xx-xxxx
mainfont: Droid Sans Fallback
---
```
The second way is to use the `g:papyrus_pandoc_args` variable in your `init.vim` or `.vimrc` file:
```vim
let g:papyrus_pandoc_args = '-V mainfont="Droid Sans Fallback"'
```
### Templates
Papyrus supports two templates which you can view in the [pdf directory](https://github.com/abeleinin/papyrus/tree/main/templates/pdf). Custom template files can be created using [pandoc-latex-templates](https://github.com/Wandmalfarbe/pandoc-latex-template). If you create a cool template feel free to submit a pull request!
```vim
" Specify the current template by its file name
let g:papyrus_template = 'default'
```
### Default
### Lecture
## Demo
This is a demo from my notes on the [Book of Proof](https://www.people.vcu.edu/~rhammack/BookOfProof/Main.pdf). I'm using the [Vim Pandoc Syntax](https://github.com/vim-pandoc/vim-pandoc-syntax) plugin to automatically insert special characters and clean up the document. Also, in the demo, you can see that pandoc supports the ability to insert Latex syntax inside the Markdown document.
https://user-images.githubusercontent.com/95333017/220041898-7326b76d-348e-4bf4-95dd-b4a879527ed5.mov