Tim Pope's vim-surround defines mapping ys{motion}l in normal mode and Sl in visual mode to surround a motion with an LaTeX environment. It might be nice to mention this somewhere in the documentation?

Thanks for this great plugin! :)

Hi, I am trying to add a reference list at the end of the document and cite them in the main text. I have a bib file named "biblio.bib" which has the following content and put into the src folder of the project:

@inproceedings{wrigstad2017mastery,
    Author =       {Wrigstad, Tobias and Castegren, Elias},
    Booktitle =    {SPLASH-E},
    Title =        {Mastery Learning-L

Related to issue #577, I would really like tectonic to give me the option to make warnings fatal.

问题描述:

现在让用户去 issue 中寻找解决思路的方法不太友好

系统信息:

• OS版本(带版本号): macOS/Windows/Linux
• TeX 发行版(带版本号): TeX Live/MiKTeX/MacTeX

日志信息:

The current tufte-book documentation has no guidance on the how to display epigraphs. Use of the \epigraph package seems incongruous with the general style and theme of the tufte-book class. Could guidance be given on a way to display quotes at the beginning of a chapter?

Environment

• TeXstudio: 2.12.10
• Qt: 5.8.0
• OS: Windows 7
• TeX distribution: miktex

How to reproduce

The options menu contains the commands "Load Profile..." and "Save Profile...".
These commands should be described in Help->"User Manual", but they aren't.

The title says it all, I think. They used to be aligned in previous versions.

I use this PDF with my students in a middle school. They have commented that they think the diagrams aren't big enough, especially compared to the pages from the orginal Byrne which I was giving them. Compare, just as an example, Book 1 Prop 13. The original is much "chunkier" (in the words of my students.) Is it possible to easily change the size of the diagrams, or would that require a complete

I am a novice at Go, so this might have an obvious reason/solution, however I have run into a problem on the first page of the book. It says to use godoc hash to read about the hash package. I tried that and it says this:

Unexpected arguments. Use "go doc" for command-line help output instead. For example, "go doc fmt.Printf".
usage: godoc -http=localhost:6060

When using `go doc

It would be useful to be able to specify a label for the spells. That would allow hyperlinking from a spell list to a spell description. The following is a suggestion/use-case:

\section{Spell List}
…
\hyperlink{Some Magic}{spell:some-magic}
…

\section{Spell Descriptions}
…
\begin{spell}[label=spell:some-magic]
    {Some Magic}
    …
\end{spell}
…

I think it would be cool to add a type of b/w and a colour version for each available template. It would be very helpful for printing the resumes.

The current documentation states for the "add-confirm" setting that: "If set to True, every time you run papis add the flag --confirm will be added automatically." This would seem to imply that the default value (False) prevents the confirmation message from showing up when you run "papis add [file]" from the command line. However, one must include the --batch flag in order to accomplish that (add

Version: 3.1.5b

On page 1164, the documentation to \pgfpointtransformednonlinear reads:

Works like \pgfpointtransformed, but also applies the current nonlinear transformation...

However, \pgfpointtransformed is not documented at all - but it really should be, I'd say it is rather a rather important function.

For developers, it would also be nice to know what the recommended way

Katex allows for a number of options to be passed such as macros but right now only error color seems to be implemented.

Would you accept a PR to implement macros?

Great tool!

I would like the option to output into formats other than HTML, or maybe even into HTML with a different mapping from latex environments to HTML tags. Any you could publish a summary of the AST format produced by the PEG.js parser, so others (like me) can write associated transformers?

• I have read the MiKTeX Contributing Guidelines

This is a usability issue I have found by observing others (researchers) and then attempting to assist them.

On the download and installation instructions page for Ubuntu Linux on MiKTeX.org it is unclear that there are post-install instructions. When an installation doesn't f

Currently I'm gathering some insights on how the DefaultTexFont.xml is constructed.

Before we do anything adventurous such as merging #156, we need to have complete insight on the innards of this XML file.

This task is a prerequisite for #43, #107, #109 (yep, that's an interesting one), and #156.