>>>>> Ikumi Keita <[email protected]> writes:
> Hi developpers, I'd like to commit a change proposed in
> https://lists.gnu.org/archive/html/auctex/2018-05/msg00014.html in
> order to resolve problems addressed in
> https://lists.gnu.org/archive/html/auctex/2018-05/msg00003.html
> https://lists.gnu.org/archive/html/auctex/2018-05/msg00004.html .
> Are there anyone who doesn't agree with this?
> As explained in ealier messages, this patch introduces some
> incompatibilities: - Users cannot put raw TeX codes in the command
> line like latex -interaction=nonstopmode \SOME_CODE \input
> FILENAME via setting `TeX-command-extra-options' anymore, as long
> as the default `TeX-command-list' is used. - (Pdf)latex binaries
> without e-TeX extension have the following two limitations:
> 1. Preview-latex does not work. (This can be circumvented by
> customizing `preview-LaTeX-command' and
> `preview-undump-replacements' to cancel the change by my patch,
> though) 2. Region compilation (C-c C-r, C-c C-e etc.) does not
> work. I.e., such binaries can only use C-c C-c (and C-c C-a) to
> typeset the latex documents. If you consider that these
> incompatibilities are not acceptable, please express your opinion.
> I would be ready to discuss about this.
> If no objection, I'll commit the change in a few days. Adding
> document changes and regression tests will follow later.
> Best regards, Ikumi Keita
> P.S. I tested the patch with MikTeX briefly, and encountered no
> errors.
I really do not like what I understand to be this suggestion. If users
cannot put TeX codes in a command then extensive functionality is
lost. The bar on non-ascii file names seems trivial to me - sorry.
_______________________________________________
auctex-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/auctex-devel
