Search found 73 matches

by erwann
Sun May 06, 2018 2:13 am
Forum: General
Topic: expl3: don't understand behavior of tl_if_novalue:nTF
Replies: 1
Views: 1287

expl3: don't understand behavior of tl_if_novalue:nTF

Before opening a ticket bug I'd like to make sure it is one indeed.
Code: [Select all] [Expand/Collapse] [Download] ({untitled.tex})
  1. \documentclass{minimal}
  2. \usepackage{expl3}
  3. \ExplSyntaxOn
  4. \begin{document}
  5. \tl_if_novalue:nTF{\c_novalue_tl}{PASS}{FAIL} % prints FAIL
  6. \ExplSyntaxOff
  7. \end{document}
by erwann
Sun May 06, 2018 1:54 am
Forum: Fonts & Character Sets
Topic: expl3: Nx expansion won't take math typesetting
Replies: 1
Views: 850

expl3: Nx expansion won't take math typesetting

The code below says it all. \documentclass{minimal} \usepackage{expl3} \usepackage{amssymb} \ExplSyntaxOn \begin{document} \tl_set:Nn \bar{A} \tl_set:Nf \baz{\ensuremath{\mathcal{\bar}}} %\tl_set:Nx \baz{\ensuremath{\mathcal{\bar}}} % :Nx generates error \tl_set:Nn \bar{B} \baz % want \mathcal{A}, g...
by erwann
Sun May 06, 2018 1:36 am
Forum: Fonts & Character Sets
Topic: expl3: changing the catcode such that _ is understood as subscript
Replies: 2
Views: 1135

expl3: changing the catcode such that _ is understood as subscript

cgnieder wrote:Why don't you just use LaTeX's \sb or expl3's \c_math_subscript_token?
Too obvious for me to see it. Thanks!
by erwann
Tue May 01, 2018 11:37 pm
Forum: Fonts & Character Sets
Topic: expl3: changing the catcode such that _ is understood as subscript
Replies: 2
Views: 1135

expl3: changing the catcode such that _ is understood as subscript

The example that follows says it all. \documentclass{minimal} \usepackage{expl3} \usepackage{xparse} \usepackage{amssymb} \ExplSyntaxOn \tl_set_rescan:Nnn \tl_matrix_elem {\char_set_catcode_math_subscript:n \_} %Wrong guess, apparently {\ensuremath{A_{ij}}} \NewDocumentCommand\matrixelem{}{\tl_matri...
by erwann
Wed Apr 25, 2018 10:51 pm
Forum: General
Topic: Specifying arguments with xparse Topic is solved
Replies: 12
Views: 4405

Specifying arguments with xparse Topic is solved

It's odd the last piece of code I pasted (E arguments) no longer works on Linux. ! Undefined control sequence. l.19 \foo _{one}^{two} This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./argE.tex LaTeX2e <20...
by erwann
Mon Mar 19, 2018 11:46 pm
Forum: General
Topic: expl3 for dummies Topic is solved
Replies: 13
Views: 5699

expl3 for dummies Topic is solved

OK, thanks.

Maybe internal/public should be renamed private/public or internal/external or implementation/interface?
by erwann
Mon Mar 19, 2018 9:24 pm
Forum: General
Topic: Specifying arguments with xparse Topic is solved
Replies: 12
Views: 4405

Specifying arguments with xparse Topic is solved

I would have thought the 'chars' in e{chars} or E{chars} would have been specified as '_^' rather than '^_' given the example that follows. I get it now... xparse.pdf: "returned data is a token list comprising one braced entry per key, ordered as for the key list in the argument specification....
by erwann
Sat Mar 17, 2018 6:30 pm
Forum: General
Topic: Automating sty and doc generation
Replies: 2
Views: 1525

Automating sty and doc generation

Partial answers: If I need to describe \themacro\oarg{X}\marg{Y} I would say "option \meta{X} is... and argument \meta{Y} is ..." (see ltxdoc.pdf). However, if the option is of the form key=val, using \meta won't look right. I don't know how to typeset these for sure (if someone would like...
by erwann
Fri Mar 16, 2018 6:33 pm
Forum: General
Topic: Automating sty and doc generation
Replies: 2
Views: 1525

Automating sty and doc generation

Ancillary question: I see

Code: [Select all] [Expand/Collapse] [Download] ({untitled.tex})
  1. ^^A


pop up in some of ctan's dtx. What is it, what pckg is it using?
by erwann
Fri Mar 16, 2018 2:43 am
Forum: General
Topic: Automating sty and doc generation
Replies: 2
Views: 1525

Automating sty and doc generation

Please help modify the pieces of code in CAPITAL letters to make this work. code.sty: % \begin{macrocode} \NeedsTeXFormat{LaTeX2e} \ProvidesPackage{foo} \usepackage{xparse} \ExplSyntaxOn % \end{macrocode} % Some internal: % \begin{macro}{NAME} % \begin{macrocode} \cs_new:Npn \ewann_impl:n #1 { (...

Go to advanced search