[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: jfbu
Subject: Re: [AUCTeX-devel] Typeset LaTeX files with non-ascii file name in TeXLive 2018
Date: Mon, 21 May 2018 14:17:29 +0200
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Le 21/05/2018 à 14:06, jfbu a écrit :
Hi Arash

Le 21/05/2018 à 12:26, Arash Esbati a écrit :
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"

Surely Keita (sorry Keita for mixing up your firstname with lastname!)
will know better
than me but from brief look at the patch %(extraopts) is still there.

More precisely for LaTeX compilation it is inserted via

LaTeX-command-style is a variable defined in ‘tex.el’.
Its value is
(("" "%(PDF)%(latex) %(file-line-error) %(extraopts) %S%(PDFout)"))

which to best of my knowledge is not affected by Keita's patch.



The only thing is that it can't be used with TeX macros like \def\x{blurp}
if the file is not processed then via \input.

The documentation in tex.el says

"String with the extra options to be given to the TeX processor."

it does not mention possibility to use it for inserting TeX macros
before inputting the file for processing. Do AUXTeX users employ it
this way?

The patch has no impact on -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.

Best, Arash


reply via email to

[Prev in Thread] Current Thread [Next in Thread]