pandoc/test/command/write18.md

Handle \write18{..} as raw tex:
```
% pandoc -t native
\write18{git --version}
^D
[RawBlock (Format "tex") "\\write18{git --version}"]
```

```
% pandoc -f latex+raw_tex -t native
\write18{git --version}
^D
[RawBlock (Format "latex") "\\write18{git --version}"]
```
Make sure \write18 is parsed as raw LaTeX. The change is in the LaTeX reader's treatment of raw commands, but it also affects the Markdown reader. 2017-07-12 13:58:47 +02:00			`Handle \write18{..} as raw tex:`
			```
			`% pandoc -t native`
			`\write18{git --version}`
			`^D`
Markdown reader: Use "tex" instead of "latex" for raw tex-ish content. We can't always tell if it's LaTeX, ConTeXt, or plain TeX. Better just to use "tex" always. Also changed: ConTeXt writer: now outputs raw "tex" blocks as well as "context". (Closes #969). RST writer: uses ".. raw:: latex" for "tex" content. (RST doesn't support raw context anyway.) Note that if "context" or "latex" specifically is desired, you can still force that in a markdown document by using the raw attribute (see MANUAL.txt): ```{=latex} \foo ``` Note that this change may affect some filters, if they assume that raw tex parsed by the Markdown reader will be RawBlock (Format "latex"). In most cases it should be trivial to modify the filters to accept "tex" as well. 2018-08-15 19:25:12 +02:00			`[RawBlock (Format "tex") "\\write18{git --version}"]`
Make sure \write18 is parsed as raw LaTeX. The change is in the LaTeX reader's treatment of raw commands, but it also affects the Markdown reader. 2017-07-12 13:58:47 +02:00			```

			```
			`% pandoc -f latex+raw_tex -t native`
			`\write18{git --version}`
			`^D`
			`[RawBlock (Format "latex") "\\write18{git --version}"]`
			```