From: sven.androd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: luatex-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org
Subject: Re: How to use LaTeX command "\write18{}" in Pandoc
Date: Sat, 15 Jul 2017 04:22:10 -0700 (PDT) [thread overview]
Message-ID: <826afb01-9b76-452d-8aaa-6ecef81881ca@googlegroups.com> (raw)
In-Reply-To: <xrwf1rqnc3pu.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1512 bytes --]
Thank you! I did not know about that package, but that seems like a more
appropriate solution.
// Sven
Den torsdag 13 juli 2017 kl. 16:32:04 UTC+2 skrev Ulrike Fischer:
>
> Am Wed, 12 Jul 2017 13:43:54 +0200 schrieb John MacFarlane:
>
> > I can modify the LaTeX reader so it handles this special
> > case better. (A LaTeX control sequence must be a sequence
> > of letters -- here the '18' specifies a file handle, I
> > think.)
> >
> > In the mean time, try defining a macro synonym:
> >
> > \newcommand{\mywrite}[1]{\write18{#1}}
> >
> > and then use `\mywrite`.
>
> There is no need for an own command. Load the shellesc package and
> use
>
> \ShellEscape and \DelayedShellEscape
>
> instead of \immediate\write18 and \write18 -- it is recommended
> anyway as it has the benefit to also work with luatex where \write18
> no longer exists.
>
>
>
> --
> Ulrike Fischer
> http://www.troubleshooting-tex.de/
>
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/826afb01-9b76-452d-8aaa-6ecef81881ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2648 bytes --]
prev parent reply other threads:[~2017-07-15 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 8:10 sven.androd-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <9a1c3693-5d46-4de0-921b-3408ca893bad-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-12 11:43 ` John MacFarlane
[not found] ` <20170712114354.GA21458-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2017-07-12 12:04 ` sven.androd-Re5JQEeQqe8AvxtiuMwx3w
2017-07-13 14:31 ` Ulrike Fischer
[not found] ` <xrwf1rqnc3pu.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2017-07-15 11:22 ` sven.androd-Re5JQEeQqe8AvxtiuMwx3w [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=826afb01-9b76-452d-8aaa-6ecef81881ca@googlegroups.com \
--to=sven.androd-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=luatex-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).