Re: [AUCTeX-devel] Typeset LaTeX files with non-ascii file name in TeXLive 2018

[Colin Baxter]

>>>>> Arash Esbati <address@hidden> writes:

    > Ikumi Keita <address@hidden> writes:
    >> The difference between my two patches are summarized below:
    >> 1. Previous patch Good points: - LaTeX format version banner is
    >> not discarded in the log file. [1] - First line parsing is not
    >> disabled. [2] - Bug#25276 is fixed. [3] Bad points: - Users
    >> cannot put TeX codes in a command line by default.  2. New patch
    >> Good points: - Users still can put TeX codes in a command line.
    >> Bad points: - LaTeX format version banner is discarded in the log
    >> file by default.  - First line parsing is disabled by default.  -
    >> Bug#25276 remains.
    >> 
    >> I still prefer the approach of the previous patch, but will honor
    >> your opinion if you are still against it.

    > Hi Keita,

    > many thanks for working on this.  I haven't looked at the patch,
    > but I think we should keep `TeX-command-extra-options' working.
    > It is a very flexible way to control the binary invoked on a file
    > basis.  E.g., all files which \usepackage{minted} need this:

    >     %%% TeX-command-extra-options: "-shell-escape"

    > I'm not sure if first line parsing is so important.  The issue
    > described here[1] can be solved with

    >     %%% TeX-command-extra-options: "--fmt=foo.fmt"

    > Hence, I'm voting to keep this feature running and drop something
    > else.

I agree.