Re: [AUCTeX] overlay prompting

[jfbu]

Bonjour Vincent

let's take a risk and reply without testing either ;-)

I trust the \^^64ocumentclass will fool the AUCTeX parser (it should ;-) )
but the problem is that within a verbatim the ^ is sanitized to catcode 12.
Thus the latex run will actually print verbatim ^^64.

The ^^ input form needs ^ to be of catcode 7.

It actually works with any catcode 7 character (I used this in the source
of a package). For example && if you do \catcode`& 7.

But & is also sanitized by verbatim:

~$ latexdef dospecials

\dospecials:
macro:->\do \ \do \\\do \{\do \}\do \$\do \&\do \#\do \^\do \_\do \%\do \~

and besides, I may need it to naturally for tabulars.

Thus this approach would need at least the same amount of preparation
as the technique of \doc¡umentclass which I adopted near the end of the
thread (which works using \catcode`\¡ 9 ).

Best, Jean-François

Le 29 févr. 2016 à 23:38, Vincent Belaïche <address@hidden> a écrit :

> Salut Jean-François,
> 
> Not tested idea : 
> 
> Can't you fool the parser by writing \^^64ocumentclass instead of 
> \documentclass when you are inside the verbatim env.
> 
> I guess that the ^^64 is parsed by TeX input processor, so it is not 
> sensitive to verbatim catcodification. Am I wrong ?
> 
>    Vincent.
> 
> ----------------------------------------
>> To: address@hidden
>> From: address@hidden
>> Date: Mon, 25 Jan 2016 22:45:40 +0100
>> Subject: Re: [AUCTeX] overlay prompting
>> 
>> Hi Mosè,
>> 
>> Le 25/01/2016 21:21, Mosè Giordano a écrit :
>>> Hi Jean-François,
>>> 
>>> 2016-01-25 10:08 GMT+01:00 jfbu <address@hidden>:
>>>> My document has other AUCTeX-parsing related problems. For example
>>>> 
>>>> \begin{verbatim}
>>>> \usepackage{fontspec}
>>>> \end{verbatim}
>>>> 
>>>> similarly triggers AUCTeX to prompt me for xetex/luatex compilation.
>>>> This made the workflow a bit painful, but I forgot about it last time
>>>> as I was doing latex runs via a Makefile.
>>> 
>>> (setq TeX-check-engine nil)
>>> 
>>> makes the warning go away.
>> 
>> ah yes, actually you already told me so in the fontspec thread,
>> thanks for reminding me
>> 
>>> 
>>>> Also, perhaps commands like \setmainfont also make AUCTeX's parser react,
>>>> or is it only \documentclass and \usepackage ?
>>> 
>>> \setmainfont isn't parsed.
>> 
>> ok, then perhaps I will do the ¡ trick after all.
>> 
>> Rather than \let¡\empty, I could also simply do \catcode`\¡ 9
>> to tell TeX/LaTeX to ignore it rather than have it be active
>> (which it is via \usepackage[latin1]{inputenc}) with an empty
>> expansion
>> 
>> best regards,
>> 
>> Jean-François
>> 
>> 
>> _______________________________________________
>> auctex mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/auctex
>