LAURENS Jérôme

IMHO, considering N as a required base type is not sufficient because the 'c' to 'N' conversion need not be straightforward. For example, `\newcounter` conceptually takes a 'c' argument but...

Not really, a 'c' type argument gets expanded whereas an 'n' argument not.

Very clear indeed. I suggest to amend the documentation of `\cs_generate_variant:Nn`: - at the top, mention that the ⟨original argument specifier⟩ must only contain N or n (apart trailing T...

According to `interface3.pdf` p 15, base functions can only have n, N, T, F, p, w argument specifiers, the p and w arguments should be removed to conform to the...

I can generate a `NV` variant of `\cs_set:Nn` and use it properly. I can generate a `Npo` variant of `\cs_set:Npn` and use it properly. I can generate a `NpV` variant...

The `p` bonus should definitely be the purpose of a TeX hackers note. If my understanding is correct, it is possible to drop down the 'NpV' variant and replace ```...

It can be documented multiple times. Near `NewDocumentCommand` and friends is useful to justify some kind of rule of thumb: avoid optional arguments in last position when possible.

Thanks Maybe the ltluatex documentation can better highlight luatexbase.sty. Actually it is hidden in the Plain TeX section... and like many people, I very seldomly read Plain TeX sections ;-)

My own use case: ```latex \begin{verbatim} Line 1 Line 2 |\textbf{This is bold text}| \end{verbatim} ``` The part between the `|` is typeset with the real catcode regime, including 3rd...

The workflow: 1. save the current catcode regime in one of the scratch variables 2. make any catcode modification, either local or global 3. typeset material either in saved or...