Currently it is not. The viewer is started by means of
`TeX-run-discard' which discards the process output, see
`TeX-command-list'. Formerly `TeX-run-silent' was used which would
generally allow for the output to be gathered and shown, but this
did not work with xdvi detaching itself from
I tried to debug why `start-process' (i.e. `TeX-run-silent') fails
when `process-connection-type' is nil, xdvi is started with source
specials enabled and has to create fonts. During debugging a PK
file was actually created and an xdvi window showed up as soon as
`vfork' was called in
[commit 4b66b9f60e3ce4a552bd4f3230b659347add1446,
Fri Jan 12 11:32:18 2018 +0100]
Folks,
I have the following local variables for a .tex file:
%%% Local Variables:
%%% mode: japanese-latex
%%% coding: utf-8
%%% TeX-engine: uptex
%%% TeX-PDF-from-DVI: "dvipdfmx"
%%% TeX-master: t
[git commit 4b66b9f60e3ce4a552bd4f3230b659347add1446]
Folks,
I have the following in my master document.
%%% Local Variables:
%%% coding: utf-8
%%% mode: latex
%%% TeX-engine: xetex
%%% TeX-PDF-mode: t
%%% TeX-master: t
%%% End:
However, the `*xxx output* buffer (showing the
> AUCTeX determines the coding system for reading from the output of
> asynchronous TeX process by the function
> `TeX-adjust-process-coding-system'. It basically obeys the coding
> system of the command buffer, i.e., the buffer in which `C-c C-c' or
> something like it is issued. So I expect
>> My question was probably not precise enough: I wonder why auctex
>> doesn't set the buffer encoding also (derived from the master
>> file's local variables), given that auctex itself generates the
>> *xxx output* buffer.
>
> Because the output buffer *xxx output* rarely needs to be saved in a
>> My question was probably not precise enough: I wonder why auctex
>> doesn't set the buffer encoding also (derived from the master
>> file's local variables), given that auctex itself generates the
>> *xxx output* buffer.
>
> TeX is an 8-bit program wrapping its output, [...]
I was
>> The only thing which looks strange to me is that, the mode line in
>> the `*xxx output* buffer starts with
>>
>> 1:**
>> (but the UTF-8 contents of the log file as emitted by XeTeX is
>> correctly displayed).
>
> In that case, latin-1 is the coding system for saving that buffer
> and utf-8 is
> [...]
>
> Thus maybe AUCTeX can now change the default value of
> `TeX-kpathsea-path-delimiter' to ";" and announce to users who use
> old TeX distribution where kpsewhich command doesn't accept ";" as
> path delimiter that "Update your TeX distribution or customize
>
> 1. Customize `TeX-kpathsea-path-delimiter' to ";".
Is there a reason why ';' is not the default? The kpathsea library
can use this value for non-Windows systems, too – have a look into
TeXLive's `texmf.cnf` file, for example.
Werner
[auctex git version around May 11th, 2023]
If I have a document like this
```
\documentclass{article}
\usepackage{fvextra}
\DefineShortVerb{\|}
\begin{document}
|foo|
\end{document}
%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% LaTeX-shortvrb-chars: (?|)
%%% End:
```
`|foo|`
> I installed a change (fe3ef154) and now fancyvrb.el supports
> verbatim characters OOTB. Note that you have to set
> `LaTeX-fancyvrb-chars'. Do you want to give it a roll?
It works fine, thanks for the quick fix!
Werner
> You could try something like this in your .tex file:
>
> \usepackage{shortvrb,fvextra}
Yeah, I considered that too but ...
> It shouldn't break your .tex file and will help AUCTeX to DTRT.
... the phrase *shouldn't* is not something I really like :-)
>> Or maybe it makes sense to always
The attached two patches make `./autogen.sh` run without warnings.
Werner
>From 6154ebc4e11856bbffab8cad24895083c7175d8c Mon Sep 17 00:00:00 2001
From: Werner Lemberg
Date: Mon, 1 Aug 2022 16:33:11 +0200
Subject: [PATCH 1/2] Fix `autoconf` warnings
* configure.ac: Run `autoupd
If syntax highlighting is on, auctex handles `\def\section' as if it
were a plain \section command. Maybe it makes sense to handle \def
specially, suppressing any fontification for the keyword after it.
Werner
==
Emacs
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.
Be sure to consult the FAQ section in the manual before submitting
a bug report. If the bug (or problem) is triggered by a specific
(La)TeX file, you should try to produce a minimal sample file
Meanwhile I've found the documentation w.r.t. » and « :-)
I suggest to disable this functionality until the user explicitly
activates it. Fontification is too painful IMHO if the user tries the
German style while the default is for French.
Werner
What I am thinking of is that when one of the quotation marks which
can be used in French or German style is found the first time during
fontification, the buffer will be searched from beginning to end for
the first occurence of the quotation mark type and that will
determine the style to be
>> The attached two patches make `./autogen.sh` run without warnings.
>
> Thanks, I tested them locally and they both work. I have one question
> though: Does your change means that building AUCTeX requires a minimum
> version of autoconf? I'm in general easy with it, we should only
> mention
001
From: Werner Lemberg
Date: Mon, 1 Aug 2022 16:33:11 +0200
Subject: [PATCH 1/2] Fix `autoconf` warnings
* configure.ac: Run `autoupdate`.
* aclocal.m4: s/AC_FD_CC/AS_MESSAGE_LOG_FD/.
---
aclocal.m4 | 6 +++---
configure.ac | 5 +++--
2 files changed, 6 insertions(+), 5 deletions(-)
diff --
[commit 0cb158fd96ff8c1c7f0bf8c0dd152a301e82f562]
Consider this quite complicated Texinfo macro file from LilyPond's
documentation:
https://gitlab.com/lilypond/lilypond/-/blob/master/Documentation/ca/macros.itexi
If I call `TeX-fold-buffer`, some macros like `rnotation` are
properly
> If I call `TeX-fold-buffer`, some macros like `rnotation` are
> properly folded, but many others like `snippets` or `englishref` are
> not.
Ah, maybe it is not working for `@macro ... @end macro` either – the
`[r]` seems to be a reference, not the contents of a macro.
Werner
>> It seems that the presence of a `@xxx` command within a macro
>> causes hiccups, but as `englishref` shows, other factors seem to
>> play a role, too.
>
> I'm not sure if I understand this part. Can you please give me a hint
> where to look in that file and what to do in order to understand
> [...] if you look here[1], you'll see:
>
> The variables TeX-fold-macro-spec-list, TeX-fold-env-spec-list,
> and TeX-fold-math-spec-list apply to any AUCTeX mode. If you want
> to make settings which are only applied to LaTeX mode, you can use
> the mode-specific variables
> Without looking at the code, it seems that it does not consider the
> first thing behind @macro to be an argument.
Thanks for the reply; I got this impression, too.
Given that I have no idea about the internals of AUCTeX I can't help
with coding; however, I'm willing to test any new Texinfo
25 matches
Mail list logo
