Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <e7ce363c-c154-50b7-016f-0f98bf13a0b9@gmail.com>
Date:   Thu, 10 Feb 2022 10:43:34 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: [PATCH] docs: Makefile: Add -no-shell-escape option to LATEXOPTS
Content-Language: en-US
To:     Jonathan Corbet <corbet@lwn.net>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        Akira Yokosawa <akiyks@gmail.com>
References: <519bd2d9-1bee-03e1-eeb4-d9883c18be0c@gmail.com>
From:   Akira Yokosawa <akiyks@gmail.com>
In-Reply-To: <519bd2d9-1bee-03e1-eeb4-d9883c18be0c@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 10 Feb 2022 10:26:53 +0900,
Akira Yokosawa wrote:
> By adding this option, message of "restricted \write18 enabled" from
> LaTeX can be silenced.
> 
> As there is no use of \write18 in LaTeX sources from sphinx-build, it
> is safe to add this option.

Jon,
JFYI, there is a ticket on the message at:

    https://tex.stackexchange.com/questions/76105/what-does-restricted-write18-enabled-mean-and-why-does-texlive-keep-reporting

I think David Carlisle's answer covers most of your concerns.

        Thanks, Akira 

> 
> Reported-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> ---
[...]