auctex
[Top][All Lists]
Advanced

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

Re: [AUCTeX] files with non-ascii characters and LaTeX as in TeXLive 201


From: Ikumi Keita
Subject: Re: [AUCTeX] files with non-ascii characters and LaTeX as in TeXLive 2018
Date: Fri, 11 May 2018 22:24:02 +0900

Hi Mosè and David,

>>>>> David Kastrup <address@hidden> writes:
> Mosè Giordano <address@hidden> writes:

>> I seem to remember David explained that "\input" was used to make
>> something work (region-compilation?).  I looked for this explanation
>> in my inbox but I can't find it, hopefully David can tell us more.  If
>> "\input" is really not needed anymore then removing "\input" when
>> calling TeX is a good solution.

> I think it was for setting interaction mode in a reasonably portable
> way.  At the current point of time, we likely just have to deal with
> MikTeX and TeXlive.

Thank you for responses.  I performed search on the ML archive and seem
to find the David's message which Mosè mentioned:
https://lists.gnu.org/archive/html/auctex-devel/2008-05/msg00055.html

First, David worried about the case some TeX codes are put on the
command line like this:
        latex -interaction=nonstopmode \SOME_CODE FILENAME
My impression is that such case is extremely rare, at least when the
default `TeX-command-list' is used.  (In theory, a user can put TeX
codes by either setting `TeX-command-extra-options' or customizing
`TeX-expand-list' to override the default expansion of the directives
such as "%(mode)", "%(file-line-error)" and so on, but...)  So I expect
we can live without \input as long as we take care of preview-latex to
work with \input.
David, what do you think about this?

Next, David pointed out that removing \input does not help %&-parsing of
the first line in the case of region compilation.  (This is not a reason
that \input is necessary, I think.)
This is a problem I looked over, and I expect that the attached
additional patch covers the point.

Regards,
Ikumi Keita

P.S.  Two notes about my previous patch
(1) According to texdoc etex, \detokenize was added in e-TeX extension.
So if the user has quite old TeX distribution where e-TeX extension was
not incorporated in the engine (command binary) yet, \detokenize raises
error.  I hope this is a permissible incompatibility.

(2) This patch incidentally fixes Bug#25276:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25276
The problem is present only in xetex engine on w32 platform.  Both the
form without \input and with \input \detokenize{} works well even when
the file name contains space, while the form with \input only (original
AUCTeX form) stops with an error.

Attachment: tex-region-create-patch
Description: additional patch


reply via email to

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